Decision question

What is confirmed about this campaign, how does it gain access and create impact, who and what are in scope, what remains unknown, and which defensive actions follow from the retained evidence?[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Interpreted questions

Review access prerequisites, reachability, exploitation, affected technology, actors, victims, timeline, tradecraft, impact, attribution boundaries, mitigation, and related IntelliOS coverage.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Initial observations

SonicWall, Rapid7, and Volexity establish a July CVE-2026-15409/CVE-2026-15410 exploitation chain that can produce root appliance compromise. Source-qualified reporting separately associates continued weaponization with INC Ransom, while Volexity tracks its observed activity as UTA0533. Hunt.io adds a separate unattributed post-disclosure CVE-2026-15409 cluster reconstructed from attacker infrastructure: 250 exploitable target identifiers, LDAP configuration recovered from 168 targets, SAM/LSA theft in at least nine Active Directory domains, and full DCSync in five. Hunt.io does not establish CVE-2026-15410 use, ransomware, INC, UTA0533, or country attribution.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Evidence hierarchy and boundary

Cross-source reconciliation of vendor, government, primary incident-response, vulnerability, and major cybersecurity-news reporting[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

SonicWall, Rapid7, and Volexity establish a July CVE-2026-15409/CVE-2026-15410 exploitation chain that can produce root appliance compromise. Source-qualified reporting separately associates continued weaponization with INC Ransom, while Volexity tracks its observed activity as UTA0533. Hunt.io adds a separate unattributed post-disclosure CVE-2026-15409 cluster reconstructed from attacker infrastructure: 250 exploitable target identifiers, LDAP configuration recovered from 168 targets, SAM/LSA theft in at least nine Active Directory domains, and full DCSync in five. Hunt.io does not establish CVE-2026-15410 use, ransomware, INC, UTA0533, or country attribution.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Compromised SMA1000 appliances can become internal attack platforms. Existing reporting establishes session, credential, TOTP, malware, and lateral-movement risk; Hunt.io additionally documents LDAP bind-password recovery, appliance-hosted secretsdump, SAM/LSA theft, domain-controller machine-account hash reuse, pass-the-hash, and DRSUAPI replication. Confirmed DCSync can require domain-wide identity recovery, not only appliance rebuild.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Upgrade 6210/7210/8200v to 12.4.3-03526 or later or 12.5.0-02952 or later; no workaround exists. Preserve evidence and assess every internet-facing pre-fix appliance. Hunt historical July telemetry for 95.181.173[.]36, http://95.181.173[.]36:80/secretsdump, SHA-256 690f5031deede7d3357d0ca24c89866ae8c60e6c63b3a2c8bba813a6ac10ae5b, /tmp/secretsdump, policy_file.xml access, appliance-origin SMB/pass-the-hash/DRSUAPI, and staged NTDS-related output. Treat the IP and URL as historical shared-infrastructure pivots. If SAM/LSA theft, machine-account exposure, or DCSync is confirmed, expand recovery to Active Directory trust. Keep the Hunt.io cluster separate from INC Ransom, UTA0533, and the September CVEs.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

SonicWall, Rapid7, and Volexity establish a July CVE-2026-15409/CVE-2026-15410 exploitation chain that can produce root appliance compromise. Source-qualified reporting separately associates continued weaponization with INC Ransom, while Volexity tracks its observed activity as UTA0533. Hunt.io adds a separate unattributed post-disclosure CVE-2026-15409 cluster reconstructed from attacker infrastructure: 250 exploitable target identifiers, LDAP configuration recovered from 168 targets, SAM/LSA theft in at least nine Active Directory domains, and full DCSync in five. Hunt.io does not establish CVE-2026-15410 use, ransomware, INC, UTA0533, or country attribution.

The retained record scopes this as zero-day edge-appliance exploitation / ransomware initial access activity during Volexity observed a separate cluster beginning 2026-06-22. Hunt.io retained post-disclosure scanning on 2026-07-16 and active exploitation on 2026-07-17. Hunt.io published its reconstruction on 2026-09-10; publication is not a first-seen date.. Compromised SMA1000 appliances can become internal attack platforms. Existing reporting establishes session, credential, TOTP, malware, and lateral-movement risk; Hunt.io additionally documents LDAP bind-password recovery, appliance-hosted secretsdump, SAM/LSA theft, domain-controller machine-account hash reuse, pass-the-hash, and DRSUAPI replication. Confirmed DCSync can require domain-wide identity recovery, not only appliance rebuild.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Upgrade 6210/7210/8200v to 12.4.3-03526 or later or 12.5.0-02952 or later; no workaround exists. Preserve evidence and assess every internet-facing pre-fix appliance. Hunt historical July telemetry for 95.181.173[.]36, http://95.181.173[.]36:80/secretsdump, SHA-256 690f5031deede7d3357d0ca24c89866ae8c60e6c63b3a2c8bba813a6ac10ae5b, /tmp/secretsdump, policy_file.xml access, appliance-origin SMB/pass-the-hash/DRSUAPI, and staged NTDS-related output. Treat the IP and URL as historical shared-infrastructure pivots. If SAM/LSA theft, machine-account exposure, or DCSync is confirmed, expand recovery to Active Directory trust. Keep the Hunt.io cluster separate from INC Ransom, UTA0533, and the September CVEs.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

Confirmed reporting is separated from attribution, victim, and prevalence claims that the retained sources do not establish. Confidence: High for official exploitation, the established July two-CVE chain, current fixes, KEV state, and Hunt.io retained-directory artifacts and outcomes; moderate for the source-qualified INC association and Hunt.io council linkage; no attribution confidence for the Hunt.io cluster..[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21]

1. 22-Jun-2026

   Earliest observed compromise

   Volexity identified the earliest compromise artifact on the first investigated SMA1000 appliance. Root-enabling tooling and the KNUCKLEBALL loader were written shortly afterward.[4]

2. 28-Jun-2026

   Exploit-chain activity recorded

   Appliance logs recorded unauthenticated /wsproxy WebSocket connections to localhost services on ports 1050 and 8188, followed by root-level hotfix-removal activity.[4]

3. 30-Jun-2026

   Additional privilege-escalation artifacts

   Volexity found additional exploitation files, including a local privilege-escalation payload later associated with CVE-2026-15410.[4]

4. 02-Jul-2026

   Credential collection on second appliance

   Artifacts showed tcpdump being used to capture unencrypted LDAP traffic. A reboot likely removed some memory-resident evidence, but malicious configuration changes remained.[4]

5. Early Jul 2026

   Incident response and lateral-movement investigation

   Volexity was engaged after suspicious authentication and lateral-movement attempts were observed from the SMA appliances; two appliances in one customer environment were confirmed compromised.[4]

6. 14-Jul-2026

   Vendor disclosure, fixes, and KEV listing

   SonicWall disclosed the vulnerabilities and fixed releases, confirmed multiple exploitation cases, and said no workaround was available. CISA added both CVEs to KEV.[1][2][6][8][9][10]

7. 15–16 Jul 2026

   Rapid7 published exploitation mechanics and IOCs

   Rapid7 described targeted pre-disclosure exploitation, credential, session, and TOTP-seed theft, and VPN-less Active Directory authentication attempts from compromised appliances; additional indicators followed on July 16.[3][8]

8. 15-Jul-2026

   Vendor product notice refined scope and recovery

   SonicWall's product notice included CMS across hypervisors and directed responders to use configuration backups only when they predate installation of the December hotfix baselines, or closely audit the configuration for tampering.[11]

9. 17-Jul-2026

   UTA0533 analysis and reported INC ransomware link

   Volexity published its UTA0533 investigation. Dark Reading separately reported Rapid7's INC association and said one active case reached ransomware deployment. The labels remain source-specific.[4][5]

10. 20-Jul-2026

    News reporting consolidated the malware findings

    BleepingComputer summarized the KNUCKLEBALL, Suo5, ORANGETAIL, ROOTRUN, credential-capture, and attempted-pivot findings while retaining Volexity's UTA0533 label.[7]

11. 03-Aug-2026

    CISA changed ransomware-use status

    CISA KEV catalog version 2026.08.03 changed known ransomware campaign use to Known for CVE-2026-15409 and CVE-2026-15410. The CVE-level field does not identify an actor or victim.[2]

12. 01–03 Aug 2026

    Continued INC weaponization receives additional support

    Resecurity assessed that INC activity accelerated and some appliances remained unpatched or compromised. The Hacker News then published a direct Rapid7 statement that INC had emerged as the dominant actor actively weaponizing the chain. Neither source establishes that INC and UTA0533 are the same identity.[12][13]

“No publicly named victim” is a disclosure statement, not an assessment that the campaign caused no harm.