Back to Intelligence

CHAOS Ransomware Gang: 3 New Victims Posted in 24 Hours — Cross-Continental Targeting Analysis & Detection Engineering

SA
Security Arsenal Team
August 25, 2026
12 min read

Classification: TLP:CLEAR | Published: 2026-08-26 | Source: Security Arsenal Dark Web Collections (ransomware.live .onion monitoring)


Executive Summary

Security Arsenal's dark web monitoring infrastructure observed three new victim postings on the CHAOS ransomware gang's Tor-based leak site within a single 24-hour window (2026-08-25). The victims span three countries — the Netherlands, the United States, and China — and cut across professional services and small-to-midsize business (SMB) verticals. This tempo and geographic scatter is consistent with CHAOS's historical pattern: opportunistic initial access via exposed edge devices and remote access tooling, followed by rapid double-extortion publication to pressure payment.

Enterprise defenders with internet-facing Check Point gateways, ConnectWise ScreenConnect instances, or unpatched Exchange/Windows estates should treat this bulletin as an immediate action item. The CVE set currently associated with CHAOS-linked intrusions maps directly to perimeter and remote-access infrastructure — the exact seams where mid-market organizations are weakest.


Threat Actor Profile — CHAOS

AttributeAssessment
Known AliasesCHAOS, Chaos Ransomware (note: distinct builders/crypter kits branded "Chaos" have circulated since 2021; the current operation is a matured RaaS offshoot with its own leak infrastructure)
Operating ModelRansomware-as-a-Service (RaaS) with affiliate recruitment on Russian-language forums; core operators maintain the leak site, negotiator portal, and builder updates
Typical Ransom DemandUSD $50K–$1.5M, scaled to victim revenue; SMB victims frequently see sub-$250K demands with 72–96 hour deadlines
Initial Access VectorsExploitation of edge/VPN appliances (Check Point, Fortinet, Ivanti-class), compromised RDP credentials (brute force + credential stuffing), phishing with macro-laden Office documents, abuse of legitimate RMM tooling (ScreenConnect, AnyDesk), and occasional initial access broker (IAB) handoffs
Extortion ModelDouble extortion — data exfiltration prior to encryption, leak-site publication in staged waves (partial dump → full dump → sale listing)
Average Dwell Time3–11 days from initial access to detonation in observed intrusions; smash-and-grab SMB cases have detonated in under 48 hours
Common ToolingCobalt Strike, PsExec, WMI/WMIC, Rclone (exfil), 7-Zip/WinRAR (staging), AnyDesk/ScreenConnect (persistence), vssadmin/wbcdmin (shadow copy deletion)

CHAOS affiliates favor legitimate-tool abuse over custom malware in the pre-encryption phase. This makes behavioral detection — not signature detection — the primary defensive lever.


Current Campaign Analysis

Victims Posted (2026-08-25)

Victim DomainSectorCountryPublished
parkderochie.comOther (recreational/consumer)NL2026-08-25
mswalker.comProfessional ServicesUS2026-08-25
copcp.comNot Found (unclassified)CN2026-08-25

Sector & Geographic Concentration

The victim mix is deliberately unglamorous: no Fortune 500 names, no critical infrastructure. This is classic CHAOS affiliate economics — a professional services firm in the US, a consumer/recreational business in the Netherlands, and an unclassified Chinese entity. Estimated victim revenue range based on sector profiling: $2M–$75M annually, squarely in the "cyber-insurance-covered but under-defended" mid-market band where ransom payment probability is highest.

The NL/US/CN spread in a single posting day indicates parallel affiliate operations rather than a single intrusion campaign. When affiliates operate concurrently, victimology tells you less about targeting intent and more about where the exploited edge devices happen to be. Organizations should not comfort themselves with "we're not in their sector" — CHAOS goes where the vulnerable perimeter is.

Posting Frequency & Escalation

Three postings in the last 100 entries, all within 24 hours, suggests a batch publication event — typically timed for maximum pressure (victims who missed negotiation deadlines get posted together). Watch for a second wave within 7–10 days as the next negotiation cohort expires.

CVE Correlation — Probable Initial Access

The CISA KEV entries currently correlated with ransomware operations map cleanly onto CHAOS's known access playbook:

  • CVE-2026-50751 (Check Point Security Gateway — improper authentication in IKEv1 key exchange): Edge-VPN compromise is CHAOS's highest-probability access vector for mid-market victims with Check Point perimeters. Unauthenticated gateway access bypasses MFA at the network layer.
  • CVE-2024-1708 (ConnectWise ScreenConnect — path traversal → RCE): RMM abuse is a documented CHAOS persistence and lateral movement mechanism. Any MSP or internal IT org running unpatched ScreenConnect is an affiliate target.
  • CVE-2025-60710 (Windows link following — privilege escalation): Post-compromise escalation primitive; pairs with stolen standard-user creds to reach SYSTEM before staging.
  • CVE-2023-21529 (Exchange deserialization → RCE): Authenticated Exchange exploitation for mailbox-dwellers — consistent with professional services targeting where Exchange on-prem persists.
  • CVE-2026-48027 (Nx Console embedded malicious code): Supply-chain flavored; developer workstations with the malicious extension become beachheads. Relevant for professional services firms with in-house dev teams.

Defensive read: if you run Check Point gateways, ScreenConnect, or on-prem Exchange and you have not patched these CVEs, assume you are in an affiliate's scan queue.


Detection Engineering

The following detections target CHAOS's documented TTP chain: edge/RMM exploitation → credential access → PsExec/WMI lateral movement → staging & exfil → shadow copy destruction → encryption.

YAML
---
title: CHAOS Ransomware - PsExec-Style Remote Service Creation (Lateral Movement)
id: 8f3a2c11-chaos-2026-0001
status: production
description: Detects remote service creation events consistent with PsExec and clone tooling (PAExec, RemCom) used by CHAOS affiliates for lateral movement prior to ransomware detonation.
author: Security Arsenal Threat Intelligence
date: 2026/08/26
references:
  - https://securityarsenal.com/darkside
logsource:
  product: windows
  service: system
detection:
  selection_event:
    EventID: 7045
  selection_service_names:
    ServiceName|contains:
      - 'PSEXESVC'
      - 'PAExec'
      - 'RemComSvc'
  selection_suspicious_paths:
    ImagePath|contains:
      - '\ADMIN$\'
      - '\IPC$\'
      - '\\Windows\Temp\'
      - '\\Users\Public\'
  condition: selection_event and (selection_service_names or selection_suspicious_paths)
falsepositives:
  - Legitimate administrative PsExec usage by IT staff
level: high
tags:
  - attack.lateral_movement
  - attack.t1569.002
---
title: CHAOS Ransomware - Volume Shadow Copy Deletion (Pre-Encryption Impact Staging)
id: 8f3a2c11-chaos-2026-0002
status: production
description: Detects deletion or resizing of Volume Shadow Copies via vssadmin, wmic, or bcdedit — a near-universal pre-encryption action in CHAOS intrusions.
author: Security Arsenal Threat Intelligence
date: 2026/08/26
logsource:
  category: process_creation
  product: windows
detection:
  selection_vssadmin:
    Image|endswith: '\vssadmin.exe'
    CommandLine|contains:
      - 'delete shadows'
      - 'Delete Shadows'
  selection_wmic:
    Image|endswith:
      - '\wmic.exe'
      - '\WMIC.exe'
    CommandLine|contains:
      - 'shadowcopy'
  selection_bcdedit:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled'
      - 'bootstatuspolicy'
  selection_powershell:
    CommandLine|contains:
      - 'Get-WmiObject Win32_Shadowcopy'
      - 'Remove-WmiObject'
      - 'vssadmin delete'
  condition: 1 of selection_*
falsepositives:
  - Backup software maintenance windows
level: critical
tags:
  - attack.impact
  - attack.t1490
---
title: CHAOS Ransomware - Data Staging and Exfiltration via Rclone or Archive Utilities
date: 2026/08/26
id: 8f3a2c11-chaos-2026-0003
status: production
description: Detects archive-based staging (7-Zip/WinRAR on sensitive directories) and Rclone execution consistent with CHAOS pre-leak exfiltration workflows.
author: Security Arsenal Threat Intelligence
logsource:
  category: process_creation
  product: windows
detection:
  selection_rclone:
    - Image|endswith: '\rclone.exe'
    - OriginalFileName: 'rclone.exe'
  selection_archive_tools:
    Image|endswith:
      - '\7z.exe'
      - '\7za.exe'
      - '\rar.exe'
      - '\winrar.exe'
  selection_archive_cmds:
    CommandLine|contains:
      - ' a -t'
      - ' -p'
      - '\\Finance\\'
      - '\\HR\\'
      - '\\Shared\\'
      - '\\Users\\'
  selection_rclone_cmds:
    CommandLine|contains:
      - 'copy '
      - 'sync '
      - 'mega'
      - 'dropbox'
      - '--transfers'
  condition: (selection_rclone and selection_rclone_cmds) or (selection_archive_tools and selection_archive_cmds)
falsepositives:
  - Legitimate backup jobs using 7-Zip; IT cloud sync tooling
level: high
tags:
  - attack.collection
  - attack.t1560.001
  - attack.exfiltration
  - attack.t1567.002
KQL — Microsoft Sentinel / Defender
// CHAOS Ransomware Hunt — Pre-Detonation Staging & Lateral Movement
// Microsoft Sentinel / Defender XDR
// Looks for: suspicious remote service installs, shadow copy tampering,
// archive staging on sensitive shares, and Rclone-style exfil — within 7 days.

let Lookback = 7d;
let SuspiciousSharePaths = dynamic(["\\Finance\\", "\\HR\\", "\\Shared\\", "\\Users\\Public\\", "\\Windows\\Temp\\"]);

// 1) Remote service creation consistent with PsExec/PAExec/RemCom
let RemoteSvc =
    Event
    | where TimeGenerated > ago(Lookback)
    | where EventLog == "System" and EventID == 7045
    | extend ServiceName = tostring(parse_xml(EventData).DataItem.EventData.Data.[0].["#text"]),
             ImagePath   = tostring(parse_xml(EventData).DataItem.EventData.Data.[1].["#text"])
    | where ServiceName has_any ("PSEXESVC","PAExec","RemCom")
         or ImagePath has_any ("ADMIN$","\\Windows\\Temp\\","\\Users\\Public\\")
    | project TimeGenerated, Computer, ServiceName, ImagePath;

// 2) Shadow copy / boot recovery tampering
let ShadowTamper =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where (FileName =~ "vssadmin.exe" and ProcessCommandLine has "delete shadows")
         or (FileName =~ "wmic.exe" and ProcessCommandLine has "shadowcopy")
         or (FileName =~ "bcdedit.exe" and ProcessCommandLine has_any ("recoveryenabled","bootstatuspolicy"))
    | project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessAccountName;

// 3) Archive staging + Rclone exfil on sensitive paths
let Staging =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName in~ ("7z.exe","7za.exe","rar.exe","winrar.exe","rclone.exe")
    | where ProcessCommandLine has_any (SuspiciousSharePaths)
         or ProcessCommandLine has_any ("--transfers","mega","dropbox"," sync "," copy ")
    | project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessAccountName;

// Correlate: devices showing 2+ behaviors are your highest-priority hosts
union RemoteSvc, ShadowTamper, Staging
| summarize BehaviorCount = dcount(TimeGenerated),
            FirstSeen = min(TimeGenerated),
            LastSeen = max(TimeGenerated),
            Indicators = make_set(ProcessCommandLine, 20)
    by Device = coalesce(DeviceName, Computer)
| where BehaviorCount >= 1
| order by LastSeen desc;
PowerShell
# CHAOS Rapid-Response Triage — run on suspected hosts or domain-wide via GPO/SCCM
# Checks: exposed RDP config, scheduled tasks added in last 7 days, shadow copy state,
# suspicious services, and RMM tool presence.

$report = @()
$cutoff = (Get-Date).AddDays(-7)

# --- 1) RDP exposure check ---
$rdpEnabled = (Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server').fDenyTSConnections -eq 0
$nlaEnabled = (Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -ErrorAction SilentlyContinue).UserAuthentication -eq 1
$rdpPort = (Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').PortNumber
$report += [pscustomobject]@{Check='RDP_Enabled'; Finding=$rdpEnabled; Risk= if($rdpEnabled -and -not $nlaEnabled){'CRITICAL - RDP on without NLA'}elseif($rdpEnabled){'Medium'}else{'Low'} }
$report += [pscustomobject]@{Check='RDP_Port'; Finding=$rdpPort; Risk= if($rdpPort -eq 3389){'Medium - default port'}else{'Low'} }

# --- 2) Scheduled tasks created in last 7 days (persistence) ---
$tasks = Get-ScheduledTask | Where-Object { $_.Date -and ([datetime]$_.Date) -gt $cutoff } |
         Select-Object TaskName, TaskPath, Date, @{n='Action';e={$_.Actions.Execute}}
foreach ($t in $tasks) { $report += [pscustomobject]@{Check='New_ScheduledTask'; Finding="$($t.TaskName) -> $($t.Action)"; Risk='High - review'} }

# --- 3) Volume Shadow Copy status (CHAOS deletes these pre-encryption) ---
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
$report += [pscustomobject]@{Check='ShadowCopies_Present'; Finding=($shadows.Count -gt 0); Risk= if($shadows.Count -eq 0){'CRITICAL - no shadow copies (tampering or never enabled)'}else{'Low'} }

# --- 4) Suspicious services (PsExec clones, random 8-char names) ---
$svcs = Get-CimInstance Win32_Service | Where-Object {
    $_.Name -match '^(PSEXESVC|PAExec|RemCom)' -or
    $_.PathName -match '\\(Temp|Public)\\' -or
    ($_.Name -match '^[A-Za-z0-9]{8}$' -and $_.PathName -match 'Users')
} | Select-Object Name, PathName, State
foreach ($s in $svcs) { $report += [pscustomobject]@{Check='Suspicious_Service'; Finding="$($s.Name) [$($s.State)] -> $($s.PathName)"; Risk='High'} }

# --- 5) RMM tooling presence (ScreenConnect/AnyDesk abused by CHAOS) ---
$rmm = Get-CimInstance Win32_Service | Where-Object { $_.Name -match '(ScreenConnect|AnyDesk|Atera|Splashtop|TeamViewer)' }
foreach ($r in $rmm) { $report += [pscustomobject]@{Check='RMM_Tool_Present'; Finding="$($r.Name) [$($r.State)]"; Risk='Review - approved inventory?'} }

# --- Output ---
$report | Sort-Object Risk | Format-Table -AutoSize
$report | Export-Csv "chaos_triage_$(hostname)_$(Get-Date -Format 'yyyyMMdd_HHmm').csv" -NoTypeInformation
Write-Host "`nTriage complete. Export written to working directory." -ForegroundColor Cyan

Incident Response Priorities

T-Minus Detection Checklist (Before Encryption Fires)

If you catch CHAOS pre-detonation, you typically win. Look for this sequence, usually 24–72 hours before encryption:

  1. New local admin accounts or group membership changes on servers, especially via net.exe or PowerShell outside change windows.
  2. PsExec-style 7045 service installs across multiple hosts within a short window (lateral movement sweep).
  3. Large archive creation (7z/rar) on file servers touching Finance, HR, or shared departmental directories.
  4. Rclone or unfamiliar cloud-sync processes with high outbound transfer volumes (check NetFlow/proxy egress spikes >50GB/day from a single host).
  5. vssadmin / wmic shadowcopy deletion — this is your klaxon. If you see it, assume detonation is minutes-to-hours away.
  6. RMM tools appearing that aren't in your approved inventory (ScreenConnect, AnyDesk, Atera).

Assets CHAOS Prioritizes for Exfiltration

  • Financial records, payroll, and HR files (leverage for "we'll notify your employees/regulators" pressure)
  • Client contracts and legal documents (professional services victims — see mswalker.com posting)
  • Domain controller NTDS.dit and credential stores
  • Backup server configurations (they want to know what you can restore — and destroy it)
  • Email archives from executive mailboxes (negotiation leverage)

Containment Actions — Ordered by Urgency

  1. Isolate the edge: Disable VPN access on any unpatched Check Point gateway; force credential rotation for all VPN-authenticated accounts (assume IKEv1-layer cred theft with CVE-2026-50751).
  2. Kill lateral movement: Disable PsExec/SMB admin share writes domain-wide via firewall policy; block outbound 445 between workstation VLANs.
  3. Terminate unauthorized RMM: Kill and quarantine ScreenConnect/AnyDesk processes not in approved inventory; block their callback domains at the proxy.
  4. Protect backups: Take backup infrastructure offline or immutable NOW; verify shadow copies still exist on critical servers.
  5. Contain identity: Disable suspicious new accounts; force KRBTGT double-reset if DC access is confirmed.
  6. Egress choke: Block unsanctioned cloud storage destinations (MEGA, Dropbox, anonymous file hosts) at the perimeter.
  7. Preserve evidence: Memory capture on the staging host before reboot; pull 7045/4624/4663 logs centrally before log wiping.

Hardening Recommendations

Immediate (24 Hours)

  • Patch Check Point Security Gateways for CVE-2026-50751 or disable IKEv1 where operationally possible; audit gateway logs for anomalous authentication attempts since June 2026.
  • Patch or retire ConnectWise ScreenConnect instances (CVE-2024-1708) — self-hosted instances are still surfacing in affiliate scans.
  • Enforce NLA + MFA on all RDP and move RDP behind VPN/ZTNA; disable direct internet exposure of 3389 entirely.
  • Enable and protect Volume Shadow Copies via GPO; alert on any vssadmin delete execution (Sigma rule #2 above).
  • Block Rclone and unsanctioned archive tooling via AppLocker/WDAC on servers holding sensitive data.
  • Apply Microsoft patches for CVE-2025-60710 and CVE-2023-21529 on Windows and Exchange estates — both are privilege-escalation/RCE links in the CHAOS chain.

Short-Term (2 Weeks)

  • Segment backup infrastructure onto isolated, immutable storage with separate credentials; assume the attacker will hunt your backups first.
  • Deploy EDR with lateral movement analytics (remote service creation, pass-the-hash, DCSync detection) — CHAOS's legitimate-tool playbook defeats signature AV.
  • Implement egress data-loss controls: alert on >10GB/day outbound from any single endpoint to non-corporate destinations.
  • Inventory and govern RMM tooling: application allowlisting for remote access software; anything not on the list is blocked and alerts.
  • Decommission or modernize on-prem Exchange — CVE-2023-21529 class bugs keep resurfacing in ransomware access chains; if Exchange stays, it gets dedicated monitoring and network micro-segmentation.
  • Tabletop a 48-hour smash-and-grab scenario — CHAOS's fastest SMB intrusions leave no time for deliberation.

Security Arsenal continues to monitor the CHAOS leak site for follow-on postings from this batch. Subscribers to AlertMonitor will receive automated victim-match notifications if their organization or supply-chain partners appear.

Related Resources

Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.