Back to Intelligence

STORM Ransomware Gang: 8 Victims Posted in 4 Days — US Financial Services Blitz, Detection Rules & IR Playbook

SA
Security Arsenal Team
September 18, 2026
14 min read

Classification: TLP:CLEAR | Publication Date: 2026-09-18 | Source: ransomware.live dark web leak site monitoring | Analyst: Security Arsenal Threat Intelligence


Executive Summary

Security Arsenal's dark web monitoring of the STORM ransomware group's .onion leak site confirms a concentrated campaign against United States organizations, with 8 victims posted between 2026-09-14 and 2026-09-18. Six of the eight victims (75%) are in Financial Services — including community banks, a credit union, and an investment counsel firm — with secondary targeting of Manufacturing, Retail, and Healthcare (PANTHERx Rare, a specialty pharmacy). The 2026-09-18 posting wave alone dropped five victims in a single day, indicating either a batch-detonation event or a coordinated leak-site publishing schedule designed to maximize pressure on victims refusing to pay.

Organizations running VMware vCenter, Cisco Secure FMC, Check Point gateways, or ConnectWise ScreenConnect should treat this briefing as an immediate action item: all four platforms map to CISA KEV entries with confirmed ransomware exploitation in the last 120 days.


Threat Actor Profile — STORM

AttributeAssessment
Known AliasesSTORM, STORM Team (leak site branding); no confirmed overlap with Storm- named Microsoft threat clusters
Operating ModelAssessed as a closed or semi-closed RaaS — leak site posting cadence and victim uniformity (US-only, mid-market) suggests a small affiliate pool or a single core operator team rather than open affiliate recruitment
Typical Ransom DemandBased on victim revenue profiles (community banks, regional manufacturers), estimated demands in the $250K–$3M range, with graduated deadlines typical of double-extortion operations
Initial AccessPerimeter device exploitation (VPN/firewall CVEs), RDP exposure, and phishing with macro or ISO-lure delivery; supply-chain tooling abuse (ConnectWise ScreenConnect) is increasingly common in mid-market intrusions
Extortion ModelDouble extortion — data exfiltration prior to encryption, leak-site publication as secondary pressure. The 4-day gap between the 09-14 and 09-18 posting batches suggests victims who failed to engage were published in bulk
Average Dwell TimeMid-market intrusions of this profile typically run 3–14 days from initial access to detonation; batch posting implies synchronized encryption events, shortening effective dwell

Analyst Note: STORM's victim selection — exclusively US, exclusively mid-market, heavily weighted toward regulated financial entities — indicates deliberate sector specialization. Community banks and credit unions often lack 24/7 SOC coverage, making them soft targets with high payment propensity due to regulatory and reputational exposure.


Current Campaign Analysis

Victimology (from live leak site data)

VictimSectorPublished
First Secure Community BankFinancial Services2026-09-18
The State BankFinancial Services2026-09-18
First Secure Bank and TrustFinancial Services2026-09-18
Johnson Investment CounselFinancial Services2026-09-18
Insight Credit UnionFinancial Services2026-09-14
American Casting CompanyManufacturing2026-09-18
McCarthy Tire ServiceRetail & E-Commerce2026-09-14
PANTHERx RareHealthcare2026-09-14

Key Observations

  • Sector concentration: 75% financial services. This is not opportunistic — it is a targeted vertical campaign against US regional banking infrastructure. Notably, three victims share "First Secure / State Bank / Insight" naming patterns consistent with small independent institutions, the exact segment least likely to have mature detection.
  • Geographic concentration: 100% United States. No cross-border victims observed in the last 100 postings analyzed.
  • Victim size profile: Community banks and credit unions (typically $100M–$2B in assets, 50–500 employees), a specialty pharmacy, a mid-size manufacturer, and a regional retail chain. Revenue estimates: $10M–$500M per victim — classic mid-market ransomware economics.
  • Posting frequency / escalation: Two batch drops (09-14: 3 victims; 09-18: 5 victims). The acceleration and the same-day multi-bank posting suggests either (a) a single perimeter vulnerability exploited across multiple targets in a short window, or (b) negotiated-deadline expirations stacking up. Both scenarios imply active, ongoing access against additional unposted victims.
  • Healthcare flag: PANTHERx Rare handles specialty/rare-disease pharmaceuticals — patient data exposure here carries HIPAA breach notification obligations and elevated regulatory risk.

CVE Correlation — Probable Initial Access Vectors

The following CISA KEV entries (all confirmed ransomware-associated) align with STORM's perimeter-first access pattern and should be treated as priority patch/compromise-assessment items:

CVEProductKEV AddedRelevance
CVE-2026-59310VMware vCenter (path traversal)2026-08-18vCenter compromise = direct hypervisor-level encryption of entire virtual estates; the highest-impact entry point for batch detonation across an org
CVE-2026-20316Cisco Secure FMC (hard-coded password)2026-07-29Firewall management plane takeover; enables policy manipulation and persistent foothold
CVE-2026-50751Check Point Security Gateway (improper auth, IKEv1)2026-06-08VPN gateway bypass — the most common initial access pattern in US mid-market ransomware cases
CVE-2026-48027Nx Console (embedded malicious code)2026-05-27Supply-chain/dev-tooling vector; possible but lower probability for this victim profile
CVE-2024-1708ConnectWise ScreenConnect (path traversal → RCE)2026-04-28MSP/RMM tooling abuse — strongly correlated with multi-victim campaigns against small financial institutions that outsource IT

Assessment: The multi-victim, same-sector, same-day pattern is most consistent with either CVE-2024-1708 (ScreenConnect) via a shared MSP or CVE-2026-50751 (Check Point IKEv1) exploited at scale. Financial institutions using outsourced IT providers running ScreenConnect should immediately audit RMM session logs.


Detection Engineering

Sigma Rules

YAML
---
title: STORM Ransomware - VPN/Perimeter Exploitation Followed by Suspicious Logon
id: 9a1f3c2e-7b44-4d21-9f0a-storm00001a
status: experimental
description: Detects successful remote logons from unusual source IPs within 24h of VPN gateway authentication anomalies, consistent with STORM's perimeter-first access via Check Point/Cisco VPN exploitation (CVE-2026-50751, CVE-2026-20316)
author: Security Arsenal Threat Intelligence
date: 2026/09/18
references:
    - https://securityarsenal.com/darkside
logsource:
    product: windows
    service: security
    category: logon
detection:
    selection_type:
        EventID: 4624
        LogonType:
            - 3
            - 10
    selection_ip:
        IpAddress|startswith:
            - '10.'
            - '192.168.'
            - '172.16.'
    filter_internal:
        IpAddress|startswith:
            - '10.'
            - '192.168.'
            - '172.16.'
    condition: selection_type and not filter_internal
falsepositives:
    - Legitimate VPN users from residential ISPs (baseline known VPN egress ranges and tune)
    - Contractors and MSP access (whitelist known MSP CIDRs — but audit them, given ScreenConnect risk)
level: high
tags:
    - attack.initial_access
    - attack.t1133
    - attack.t1078
---
title: STORM Ransomware - Lateral Movement via PsExec or WMI with Cobalt Strike-Style Named Pipes
id: 9a1f3c2e-7b44-4d21-9f0a-storm00002b
status: experimental
description: Detects PsExec service execution and WMI remote process creation combined with known Cobalt Strike default named pipe patterns observed in pre-encryption lateral movement phases
date: 2026/09/18
author: Security Arsenal Threat Intelligence
logsource:
    category: pipe_created
    product: windows
detection:
    selection_pipes:
        PipeName|contains:
            - '\PSEXESVC'
            - '\MSSE-'
            - '\status_'
            - '\msagent_'
            - '\postex_'
            - '\spoolss_'   # observed CS custom profile artifacts
    condition: selection_pipes
falsepositives:
    - Legitimate PsExec administrative use (correlate with service install EventID 7045 and source account)
level: critical
tags:
    - attack.lateral_movement
    - attack.t1021.002
    - attack.t1569.002
    - attack.s0029
---
title: STORM Ransomware - Pre-Encryption Staging and Shadow Copy Destruction
id: 9a1f3c2e-7b44-4d21-9f0a-storm00003c
status: experimental
description: Detects data staging via archive utilities to temp directories followed by Volume Shadow Copy deletion and backup catalog tampering - the canonical T-minus indicators before STORM detonation
author: Security Arsenal Threat Intelligence
date: 2026/09/18
logsource:
    category: process_creation
    product: windows
detection:
    selection_staging:
        Image|endswith:
            - '\rclone.exe'
            - '\7z.exe'
            - '\rar.exe'
            - '\winrar.exe'
        CommandLine|contains:
            - '\AppData\Local\Temp'
            - '\ProgramData'
            - 'copy'
            - 'sync'
    selection_vss:
        Image|endswith:
            - '\vssadmin.exe'
            - '\wmic.exe'
            - '\bcdedit.exe'
            - '\wbadmin.exe'
        CommandLine|contains:
            - 'delete shadows'
            - 'shadowcopy delete'
            - 'resize shadowstorage'
            - 'delete catalog'
            - 'recoveryenabled no'
    timeframe: 30m
    condition: selection_staging or selection_vss
falsepositives:
    - Legitimate backup maintenance windows (suppress via approved change ticket integration)
    - System administrators using 7z for packaging (exclude approved admin accounts)
level: critical
tags:
    - attack.impact
    - attack.t1490
    - attack.t1560.001
    - attack.t1567

KQL — Microsoft Sentinel Hunt Query

Hunt for the full pre-ransomware kill chain: remote tooling execution, staging, and shadow copy tampering within a correlated 48-hour window per host.

KQL — Microsoft Sentinel / Defender
// STORM Ransomware Pre-Detonation Hunt — correlate lateral movement + staging + VSS tampering per device
let TimeWindow = 48h;
let SuspiciousRemoteExec =
    DeviceProcessEvents
    | where TimeGenerated > ago(TimeWindow)
    | where FileName in~ ("psexec.exe", "wmic.exe", "wmiprvse.exe")
       or (FileName =~ "powershell.exe" and ProcessCommandLine has_any ("Invoke-WMIMethod", "Enter-PSSession", "New-PSSession"))
    | project RemoteExecTime = TimeGenerated, DeviceName, InitiatingProcessAccountName, ProcessCommandLine;
let DataStaging =
    DeviceProcessEvents
    | where TimeGenerated > ago(TimeWindow)
    | where FileName in~ ("rclone.exe", "7z.exe", "rar.exe", "megacmd.exe", "filezilla.exe")
       or ProcessCommandLine has_any ("rclone copy", "rclone sync", "--transfers", "mega.nz", "mega.io")
    | project StagingTime = TimeGenerated, DeviceName, StagingCmd = ProcessCommandLine, StagingAccount = InitiatingProcessAccountName;
let VSSTamper =
    DeviceProcessEvents
    | where TimeGenerated > ago(TimeWindow)
    | where ProcessCommandLine has_any ("delete shadows", "shadowcopy delete", "resize shadowstorage",
                                        "delete catalog", "recoveryenabled no", "bcdedit")
    | project VSSTime = TimeGenerated, DeviceName, VSSCmd = ProcessCommandLine, VSSAccount = InitiatingProcessAccountName;
SuspiciousRemoteExec
| join kind=inner DataStaging on DeviceName
| join kind=inner VSSTamper on DeviceName
| where StagingTime between (RemoteExecTime .. VSSTime)
| summarize FirstRemoteExec = min(RemoteExecTime), StagingEvents = count(),
            StagingCommands = make_set(StagingCmd, 5), VSSTamperTime = min(VSSTime)
  by DeviceName, InitiatingProcessAccountName
| extend KillChainWindowMinutes = datetime_diff("minute", VSSTamperTime, FirstRemoteExec)
| order by VSSTamperTime desc
// Any hit = assume active pre-encryption stage. Isolate host immediately and invoke IR plan.

PowerShell — Rapid Triage & Hardening Script

Run on suspect hosts and domain controllers. Checks for exposed RDP, recently created scheduled tasks, suspicious services, and shadow copy integrity — the four fastest validation checks against STORM's playbook.

PowerShell
# Security Arsenal - STORM Ransomware Rapid Triage Script
# Run as Administrator. Outputs findings to console + CSV for escalation.
# Usage: .	riage-storm.ps1 [-OutputPath C:\IR\]

param([string]$OutputPath = ".\STORM_Triage_$(Get-Date -Format 'yyyyMMdd_HHmm')")
New-Item -ItemType Directory -Path $OutputPath -Force | Out-Null
$findings = @()

Write-Host "[1/5] Checking RDP exposure and NLA status..." -ForegroundColor Cyan
$rdp = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -ErrorAction SilentlyContinue
$nla = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -ErrorAction SilentlyContinue
if ($rdp.fDenyTSConnections -eq 0) {
    $sev = if ($nla.UserAuthentication -ne 1) { 'CRITICAL - RDP enabled WITHOUT NLA' } else { 'WARN - RDP enabled (NLA on)' }
    $findings += [pscustomobject]@{Check='RDP Exposure'; Severity=$sev; Detail="fDenyTSConnections=0, NLA=$($nla.UserAuthentication)"}
}

Write-Host "[2/5] Enumerating scheduled tasks created in the last 7 days..." -ForegroundColor Cyan
$cutoff = (Get-Date).AddDays(-7)
Get-ScheduledTask | ForEach-Object {
    $info = $_ | Get-ScheduledTaskInfo -ErrorAction SilentlyContinue
    if ($_.Date -and ([datetime]$_.Date) -gt $cutoff) {
        $findings += [pscustomobject]@{Check='New Scheduled Task'; Severity='HIGH'; Detail="$($_.TaskName) | $($_.TaskPath) | Created: $($_.Date) | Action: $($_.Actions.Execute) $($_.Actions.Arguments)"}
    }
}

Write-Host "[3/5] Checking for suspicious services (PsExec clones, random names) installed in last 7 days..." -ForegroundColor Cyan
Get-CimInstance Win32_Service | Where-Object {
    $_.InstallDate -gt $cutoff -or $_.Name -match 'PSEXESVC|^[a-z0-9]{6,8}$'
} | ForEach-Object {
    $findings += [pscustomobject]@{Check='Suspicious Service'; Severity='HIGH'; Detail="$($_.Name) | $($_.PathName) | State: $($_.State)"}
}

Write-Host "[4/5] Validating Volume Shadow Copy integrity..." -ForegroundColor Cyan
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
if (-not $shadows) {
    $findings += [pscustomobject]@{Check='Shadow Copies'; Severity='CRITICAL - NO SHADOW COPIES EXIST'; Detail='Possible vssadmin/wmic deletion - treat as pre-encryption indicator'}
} else {
    $findings += [pscustomobject]@{Check='Shadow Copies'; Severity='INFO'; Detail="$($shadows.Count) shadow copies present, oldest: $(($shadows | Sort-Object InstallDate | Select-Object -First 1).InstallDate)"}
}

Write-Host "[5/5] Scanning for staging tools (rclone/7z/megacmd) and large recent archives..." -ForegroundColor Cyan
$stagingPaths = @("$env:TEMP","C:\ProgramData","C:\Users\Public")
foreach ($p in $stagingPaths) {
    Get-ChildItem $p -Recurse -Include rclone.exe,megacmd.exe,rar.exe -ErrorAction SilentlyContinue | ForEach-Object {
        $findings += [pscustomobject]@{Check='Staging Tool Found'; Severity='CRITICAL'; Detail="$($_.FullName) | LastWrite: $($_.LastWriteTime)"}
    }
    Get-ChildItem $p -Recurse -Include *.zip,*.7z,*.rar -ErrorAction SilentlyContinue |
      Where-Object { $_.Length -gt 500MB -and $_.LastWriteTime -gt $cutoff } | ForEach-Object {
        $findings += [pscustomobject]@{Check='Large Recent Archive'; Severity='HIGH'; Detail="$($_.FullName) | $([math]::Round($_.Length/1GB,2)) GB | $($_.LastWriteTime)"}
    }
}

$findings | Export-Csv "$OutputPath\findings.csv" -NoTypeInformation
Write-Host "`n===== TRIAGE SUMMARY =====" -ForegroundColor Yellow
$findings | Sort-Object Severity | Format-Table -AutoSize -Wrap
Write-Host "Results exported to $OutputPath\findings.csv" -ForegroundColor Green
Write-Host "If ANY CRITICAL findings exist: isolate host from network NOW and escalate to IR." -ForegroundColor Red

Incident Response Priorities — STORM Playbook

T-Minus Detection Checklist (Before Encryption Fires)

  1. vssadmin / wmic / bcdedit execution — shadow copy deletion is the single highest-fidelity pre-detonation signal. Any execution by non-backup-service accounts = page the IR team.
  2. Rclone or MEGAcmd presence — STORM-stage exfiltration tooling. Search all endpoints for rclone.exe, rclone.conf, and configs referencing MEGA, Backblaze B2, or Wasabi.
  3. Batch account creation or privilege escalation — new local admins or sudden Domain Admin additions on non-DC servers.
  4. GPO modifications — ransomware deployment at scale typically rides a modified Group Policy pushing the encryptor. Alert on any GPO change outside change windows.
  5. Backup system logins from unusual sources — Veeam/Commvault console access from non-admin workstations precedes backup destruction.
  6. ScreenConnect / RMM session audit — review all remote sessions in the last 14 days, especially from MSP tooling, for sessions outside business hours or from unknown technician IDs.

Critical Assets STORM Prioritizes for Exfiltration

  • Core banking data / customer PII and account records (for financial victims — GLBA/FFIEC reportable)
  • Loan documents, wire transfer logs, and board minutes — high embarrassment/leverage value
  • Patient records and prescription data (PANTHERx Rare pattern — HIPAA exposure)
  • HR files: SSNs, payroll, W-2s — present in nearly every double-extortion dump
  • Legal/insurance correspondence — used to calibrate ransom demands against cyber insurance coverage

Containment Actions — Ordered by Urgency

  1. Isolate, don't power off — network-quarantine affected hosts to preserve volatile memory for forensics.
  2. Disable the ingress vector immediately — if VPN/firewall CVE is suspected, take the device to fail-closed or restrict to known IPs; if ScreenConnect/RMM, revoke all sessions and rotate every credential the tool touches.
  3. Force-reset Domain Admin, service account, and KRBTGT (twice) — assume full domain credential compromise if any DC shows lateral movement indicators.
  4. Block known exfil destinations at egress — MEGA, rclone-supported cloud storage, and any unapproved outbound 443 to non-corporate storage.
  5. Snapshot/backup offline immediately — verify backup integrity before attackers finish the job for you.
  6. Engage counsel for regulatory clock-start — banks: GLBA/state notification; healthcare: HIPAA 60-day clock; the leak post itself may constitute public disclosure triggering obligations.

Hardening Recommendations

Immediate (24 Hours)

  • Patch or mitigate all five KEV CVEs listed above. Check Point IKEv1 (CVE-2026-50751), Cisco FMC (CVE-2026-20316), vCenter (CVE-2026-59310), ScreenConnect (CVE-2024-1708). If patching is not possible, restrict management interfaces to jump-host-only access.
  • Audit every RMM instance (ScreenConnect, ConnectWise, AnyDesk, TeamViewer) — enumerate active sessions, verify technician identities, disable unattended access where not operationally required.
  • Deploy the Sigma rules above to your SIEM and verify shadow copy deletion alerting fires in a test.
  • Enforce phishing-resistant MFA on all VPN and remote access — hard-coded credential and auth-bypass CVEs make password-only VPN access a coin flip right now.
  • Egress filtering: deny outbound to consumer file-sharing and sync services (MEGA, Dropbox personal, WeTransfer) at the proxy/firewall.

Short-Term (2 Weeks)

  • Segment financial core systems — core banking platforms, loan origination, and wire systems must be on isolated VLANs with allow-list-only east-west traffic. STORM's banking blitz succeeds because mid-market institutions run flat networks.
  • Implement immutable/air-gapped backups with separate credential domains; test a full restore of one critical system this sprint, not just backup job success.
  • Deploy an application allowlisting policy blocking unsigned executables in user-writable paths (Temp, AppData, ProgramData) — breaks the staging-and-detonate pattern.
  • Establish 24/7 monitoring coverage (in-house or via MDR) — batch detonations on weekends and holidays are the norm for this threat class. A community bank with no weekend SOC is exactly the victim profile on STORM's leak site.
  • MSPs as threat surface: contractually require your IT providers to disclose their RMM stack, patch SLAs, and MFA enforcement — then verify it.

This briefing is based on live monitoring of criminal leak infrastructure. Victim organizations listed have been identified publicly by the threat actor; inclusion here is for defensive purposes. Security Arsenal does not communicate with or pay threat actors.

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.