On August 10, 2026, CISA published joint advisory AA26-222a (#StopRansomware: Gunra) detailing a ransomware-as-a-service operation that has been actively targeting government agencies, critical infrastructure operators, and private sector organizations. If you run a SOC or own incident response for an at-risk organization, this advisory is not background reading — it is a tasking order.
Gunra first emerged as a ransomware variant in 2025 and scaled into a full RaaS operation in 2026, recruiting affiliates who execute intrusions against high-value targets. The operation follows the now-standard double-extortion model: affiliates encrypt victim data and exfiltrate it, threatening publication on a dedicated leak site (DLS) if payment is not made. That combination means a purely backup-centric recovery strategy is insufficient — even a perfect restore leaves you facing a data breach disclosure, regulatory exposure, and potential secondary extortion.
What makes RaaS operations like Gunra operationally dangerous for defenders is affiliate variance. The encryptor payload is consistent, but the intrusion TTPs leading to deployment vary by affiliate — different initial access brokers, different lateral movement tooling, different exfiltration staging. Your detection strategy therefore cannot key on a single IOC list. It must key on the behaviors every Gunra deployment shares: shadow copy deletion, mass file encryption, exfiltration staging, and ransom note deployment.
Technical Analysis
What We Know from AA26-222a
Based on the CISA advisory:
- Threat type: Encryption-based ransomware operated as RaaS. Core developers maintain the encryptor, decryptor, payment infrastructure, and DLS; affiliates conduct intrusions and split ransom proceeds.
- Targeting: Government entities, critical infrastructure organizations, and other enterprises. This is deliberate big-game hunting, not opportunistic spray.
- Extortion model: Double extortion — encryption plus exfiltration with DLS publication threats.
- Lineage: Variant first observed in 2025; RaaS expansion occurred in 2026.
No CVE identifiers are named in the advisory summary. That is typical for #StopRansomware publications: the initial access vector is often whatever the affiliate can buy or exploit — exposed remote services, compromised credentials, unpatched edge devices, phishing. CISA's top-line key action in the advisory is to prioritize patching known exploited vulnerabilities, which tells you exactly how these affiliates are getting in: through the same KEV-catalogued perimeter weaknesses defenders keep deferring.
The Attack Chain (Defender's View)
While affiliate playbooks vary, the Gunra operational chain consistently reduces to:
- Initial Access — Exploitation of known vulnerabilities on internet-facing systems, valid compromised accounts (frequently VPN/RDP without MFA), or phishing-delivered loaders.
- Establishment & Discovery — Persistence via accounts/services, network and domain discovery (
nltest,net group, AD enumeration), credential theft from LSASS or credential stores. - Lateral Movement — SMB/admin shares, RDP, PsExec-style service execution, and deployment tooling to push the encryptor broadly.
- Exfiltration (pre-encryption) — Staging sensitive data into archives and exfiltrating over HTTPS or via commercial RMM/file-transfer tooling. This is the phase most organizations miss.
- Impact — Mass encryption, typically preceded by anti-recovery actions: deletion of Volume Shadow Copies, clearing of backups, and disabling of recovery services. Ransom notes dropped across encrypted hosts, followed by DLS threats.
Exploitation Status
Gunra is confirmed active in the wild with government and critical infrastructure victims — that is the entire premise of a #StopRansomware advisory. This is not theoretical. Treat internet-facing asset hygiene and the behavioral detections below as an immediate operational requirement, not a backlog item.
Detection & Response
The detections below target the invariant behaviors of a Gunra deployment: shadow copy deletion, mass encryption indicators, and archive staging for exfiltration. They are designed to survive affiliate-level TTP variation.
Sigma Rules
---
title: Shadow Copy Deletion via Command-Line Utility
description: Detects deletion of Volume Shadow Copies using vssadmin, wmic, or PowerShell — a hallmark anti-recovery step executed immediately before ransomware detonation, including Gunra deployments per CISA AA26-222a.
references:
- https://www.cisa.gov/news-events/cybersecurity-advisories/aa26-222a
- https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/08/11
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith:
- '\vssadmin.exe'
- '\wmic.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\diskshadow.exe'
selection_cli:
CommandLine|contains:
- 'delete shadows'
- 'shadowcopy delete'
- 'resize shadowstorage'
- 'Delete Shadows'
- 'Win32_ShadowCopy'
condition: selection_img and selection_cli
falsepositives:
- Legitimate backup administrators resizing shadowstorage (investigate context)
- Some backup software interacting with VSS during maintenance windows
level: high
---
title: Suspicious Archive Staging for Data Exfiltration
description: Detects creation of large compressed archives in user or temp directories using common archiving tools — consistent with ransomware affiliate data staging before double-extortion exfiltration, as described in CISA AA26-222a for Gunra.
references:
- https://www.cisa.gov/news-events/cybersecurity-advisories/aa26-222a
- https://attack.mitre.org/techniques/T1560/
- https://attack.mitre.org/techniques/T1567/
author: Security Arsenal
date: 2026/08/11
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith:
- '\rar.exe'
- '\7z.exe'
- '\7za.exe'
- '\winrar.exe'
selection_cli:
CommandLine|contains:
- ' -a '
- ' a '
- '-p'
selection_paths:
CommandLine|contains:
- '\Users\'
- '\Temp\'
- '\ProgramData\'
- 'C:\\'
condition: selection_img and selection_cli and selection_paths
falsepositives:
- IT administrators archiving data for migrations
- Automated backup scripts using 7-Zip
level: medium
---
title: Ransom Note Deployment via Command Shell
description: Detects mass creation of ransom-note-style text or HTML files through cmd or PowerShell loops — a behavioral indicator of ransomware note deployment observed in Gunra and comparable RaaS operations.
references:
- https://www.cisa.gov/news-events/cybersecurity-advisories/aa26-222a
- https://attack.mitre.org/techniques/T1486/
author: Security Arsenal
date: 2026/08/11
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_shell:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
selection_cli:
CommandLine|contains:
- 'readme'
- 'decrypt'
- 'recover'
- 'restore_files'
- '.hta'
selection_loop:
CommandLine|contains:
- 'for /r'
- 'foreach'
- 'Get-ChildItem'
- 'echo'
condition: selection_shell and selection_cli and selection_loop
falsepositives:
- Administrators scripting documentation distribution (rare)
level: high
KQL Hunt — Microsoft Sentinel / Defender
This query hunts the pre-impact phase: anti-recovery commands plus suspicious process trees on endpoints. Run it across your estate daily, and treat any hit on a server or domain controller as a sev-1 investigation.
let antiRecovery = dynamic(["delete shadows", "shadowcopy delete", "resize shadowstorage", "bcdedit", "recoveryenabled no", "wbadmin delete catalog", "Win32_ShadowCopy"]);
let stagingTools = dynamic(["rar.exe", "7z.exe", "7za.exe", "megacmd", "rclone", "FileZilla"]);
DeviceProcessEvents
| where TimeGenerated > ago(7d)
| extend CmdLine = tolower(ProcessCommandLine), File = tolower(FileName)
| where (CmdLine has_any (antiRecovery))
or (File has_any (stagingTools) and CmdLine has_any (" -p", " a ", " -a ", "sync", "copy"))
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, AccountName, FolderPath
| order by TimeGenerated desc
For environments ingesting syslog/CEF from Linux and network devices into Sentinel, extend the hunt to unusual egress (exfiltration is the half of double extortion most teams miss):
CommonSecurityLog
| where TimeGenerated > ago(7d)
| where DeviceAction =~ "Allow" or isempty(DeviceAction)
| summarize TotalBytes = sum(tolong(SentBytes)), Connections = count() by SourceIP, DestinationIP, DestinationPort
| where TotalBytes > 500000000
| where DestinationPort in (443, 22, 21, 8080, 8443)
| order by TotalBytes desc
Velociraptor VQL Hunt
Use this artifact to sweep endpoints for active staging/archiving processes and anomalous outbound connections — exactly what you'd expect during a Gunra affiliate's exfiltration phase:
-- Gunra pre-impact hunt: archiving tools, shadow copy tampering, large egress
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|shadowcopy|rclone|megacmd|7z.*(-p| a )|rar.* a )'
OR Name =~ '(?i)(vssadmin|rclone|megacmd)'
-- Endpoint netstat: flag processes holding high-count outbound 443/22 connections
SELECT Pid, Name, RemoteAddress, RemotePort, Status
FROM netstat()
WHERE RemotePort in (443, 22, 21, 8443)
AND Status =~ 'ESTAB'
AND NOT RemoteAddress =~ '^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[01])\.)'
Hardening & Verification Script
Run this PowerShell audit across Windows servers and workstations (via your RMM or GPO-deployed script) to verify ransomware resilience controls are actually in place — not just assumed:
# Gunra Ransomware Readiness Audit — Security Arsenal
# Run as Administrator. Outputs PASS/FAIL per control.
$results = @()
# 1. VSS protection: confirm shadow copies exist and shadowstorage is sized
$shadows = Get-WmiObject Win32_ShadowCopy -ErrorAction SilentlyContinue
$results += [PSCustomObject]@{ Control = 'Volume Shadow Copies present'; Status = if ($shadows) { 'PASS' } else { 'FAIL - No shadow copies found' } }
# 2. Attack Surface Reduction: check ransomware-relevant ASR rules
$asr = Get-MpPreference | Select-Object -ExpandProperty AttackSurfaceReductionRules_Ids -ErrorAction SilentlyContinue
$asrActions = (Get-MpPreference).AttackSurfaceReductionRules_Actions
$needed = @('d4f940ab-401b-4efc-aadc-ad5f3c50688a','56a863a9-875e-4185-98a7-b882c64b5ce5','7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c')
$enabled = if ($asr) { $needed | Where-Object { $asr -contains $_ } } else { @() }
$results += [PSCustomObject]@{ Control = 'ASR rules (Office abuse, LSASS, ransomware)'; Status = if ($enabled.Count -ge 2) { 'PASS' } else { 'FAIL - Enable ASR rules via GPO/Intune' } }
# 3. Tamper Protection status
$tp = (Get-MpComputerStatus).IsTamperProtected
$results += [PSCustomObject]@{ Control = 'Defender Tamper Protection'; Status = if ($tp) { 'PASS' } else { 'FAIL - Enable via Intune/Security portal' } }
# 4. Real-time protection and cloud-delivered protection
$rt = (Get-MpComputerStatus).RealTimeProtectionEnabled
$results += [PSCustomObject]@{ Control = 'Defender Real-Time Protection'; Status = if ($rt) { 'PASS' } else { 'FAIL' } }
# 5. SMBv1 disabled (legacy lateral movement path)
$smb1 = (Get-SmbServerConfiguration).EnableSMB1Protocol
$results += [PSCustomObject]@{ Control = 'SMBv1 disabled'; Status = if (-not $smb1) { 'PASS' } else { 'FAIL - Disable-SmbServerConfiguration / Set-SmbServerConfiguration -EnableSMB1Protocol $false' } }
# 6. RDP exposure check: NLA required
$nla = (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -ErrorAction SilentlyContinue).UserAuthentication
$results += [PSCustomObject]@{ Control = 'RDP Network Level Authentication'; Status = if ($nla -eq 1) { 'PASS' } else { 'WARN - Require NLA or restrict RDP' } }
# 7. Local admin password hygiene: LAPS present
$laps = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\LAPS' -ErrorAction SilentlyContinue
$results += [PSCustomObject]@{ Control = 'Windows LAPS configured'; Status = if ($laps) { 'PASS' } else { 'FAIL - Deploy Windows LAPS' } }
$results | Format-Table -AutoSize
$failCount = ($results | Where-Object { $_.Status -like 'FAIL*' }).Count
Write-Host "`nAudit complete. $failCount control(s) failing. Remediate before the next shift." -ForegroundColor (if ($failCount -gt 0) { 'Red' } else { 'Green' })
Remediation & Mitigation Priorities
CISA's advisory leads with patching for a reason — Gunra affiliates monetize the gap between KEV publication and enterprise patch deployment. In priority order:
- Patch known exploited vulnerabilities on internet-facing systems first. Cross-reference your external attack surface against the CISA Known Exploited Vulnerabilities Catalog weekly. Edge devices — VPN concentrators, firewalls, mail gateways, remote access appliances — are the front door for RaaS affiliates. Do not wait for your normal patch cycle on internet-facing KEV entries.
- Enforce MFA on all remote access. VPN, RDP gateways, webmail, and third-party remote management tools. Valid-account intrusion is the cheapest affiliate access path; phishing-resistant MFA (FIDO2) on remote access closes most of it.
- Segment and restrict lateral movement. Deny workstation-to-workstation SMB/RDP by default, tier administrative access, and ensure domain controllers and backup infrastructure are in isolated segments with dedicated admin accounts.
- Protect backups as a production security control. Immutable/offline backups (3-2-1 with at least one offline or immutable copy), separate credentials for backup infrastructure, and tested restoration runbooks. Gunra affiliates hunt backup catalogs deliberately — assume
wbadmin delete catalogis coming. - Detect exfiltration, not just encryption. Double extortion means the damage window opens before detonation. Alert on large egress to unfamiliar destinations, archiving tool execution on servers, and RMM tools not in your approved inventory.
- Disable legacy protocols and harden Office. SMBv1 off, Office macros from the internet blocked, and ASR rules enabled (the script above verifies the three most ransomware-relevant ones).
- Exercise your IR plan against this scenario. Tabletop a double-extortion event: legal, comms, cyber insurance, and disclosure obligations (state breach laws, sector regulators, SEC if applicable) all trigger on the exfiltration claim even if you restore from backup cleanly.
Review the full joint advisory — CISA AA26-222a — at cisa.gov/news-events/cybersecurity-advisories/aa26-222a for the authoritative IOC set and any additional YARA/Sigma content published with it, and ingest those indicators into your SIEM and EDR blocklists immediately.
If you are a government entity or critical infrastructure operator — the named target set — treat this as an active-threat posture change, not an informational bulletin. The organizations that fare best against RaaS crews are the ones whose detections fired during staging, not during detonation.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.