Akira / REDBIKE Ransomware

M-Trends 2026 recovery-denial threat · CrowdStrike hunting, response, and hardening
Threat
Akira / REDBIKE
Type
Ransomware and recovery denial
Severity
Critical
Version
v0.3 Draft · 2026-09-04
Author
cybersecurity analyst
Confidence
High core TTP confidence; tenant behavior unverified
STATIC REVIEW PASSED
01

Executive Summary

What happened: Google Cloud Mandiant published M-Trends 2026 on 23 March 2026 and named REDBIKE, its designation for Akira ransomware activity, among prolific operations observed targeting backup infrastructure, identity services, and virtualization management planes during 2025. The November 2025 joint FBI/CISA/DC3/HHS advisory independently describes Akira activity spanning Windows, VMware ESXi, Hyper-V, and Nutanix AHV, while Check Point’s Q1 2026 review keeps Akira among the ransomware ecosystem’s dominant operators. This pack treats those public data-leak-site figures as claims, not verified incident counts.

How the chain works: observed access paths include single-factor or compromised VPN credentials, password spraying, RDP and SSH, phishing, and exploitation of vulnerable edge and Veeam systems. Once inside, operators create accounts, run nltest, net, SoftPerfect, Advanced IP Scanner, and NetScan, and pursue credentials through Kerberoasting, Mimikatz, LaZagne, or even copied domain-controller VMDKs containing NTDS.dit and the SYSTEM hive. AnyDesk, LogMeIn, RDP, SSH, MobaXterm, Impacket wmiexec.py, Ngrok, PowerShell, and WMIC support persistence, lateral movement, tunneling, and execution. WinRAR stages data; RClone, WinSCP, FileZilla, Mega, and other channels support exfiltration. Impact includes shadow-copy deletion, double extortion, and encryption of endpoint or virtualization storage.

Why detection must sit before encryption: Mandiant’s recovery-denial framing makes the durable defensive boundary the sequence around identity abuse, remote execution, security-control impairment, archive-to-transfer tooling, and recovery deletion. Q01 provides exact-hash confirmation for five advisory artifacts, while Q03 and Q06 focus on defense impairment and recovery destruction across changing payload names. Q02, Q04, Q05, and Q07 surface discovery, operator tooling, staging, and potential spreader activity but require administrative baselines. Hashes and filenames rotate, legitimate tools are dual-use, and process-only results do not prove Akira attribution.

Coverage consequence: portable endpoint telemetry cannot see VPN authentication semantics, VM power operations, disk attachment, datastore encryption, or backup-object deletion. Those require centralized identity, VPN, Veeam, VMware, Nutanix, storage, and cloud-backup audit logs. IPv6, proxy/DNS visibility, asset-role context, parser variation, and Linux or hypervisor sensor coverage remain explicit gaps. No query was executed in Falcon, no alert was scheduled, and no prevention rule was enabled; the two alert packages and one IOA are design-only validation candidates.

Defender priority: run Q03 and Q06 first over seven days, protect remaining recovery copies, then correlate any hit with Q01 and critical-server activity while preserving identity, backup, and hypervisor logs before disruptive containment.
PriorityWhy nowCoverage deliveredKey limitation
Detect control impairment and recovery deletionAkira activity is associated with recovery denial and rapid pre-impact operations7 CQL designs: 5 hunts and 2 alert candidates; 1 control-plane gapStatic review only; tenant parsing, baselines, canaries, and management-plane schemas are absent
02

Source and Claim Review

Five current-run snapshots preserve Mandiant, joint-government, Microsoft incident-response, MITRE ATT&CK, and Check Point research evidence. Every indicator remains bound to the current advisory snapshot.

IDPublisherTierIndependence groupAccessedStatus
S01Google Cloud / Mandiantprimary-incident-responsegoogle-mandiant2026-09-02T13:42:01Zcomplete-sanitized
S02FBI, CISA, DC3, HHS and international partnersgovernment-joint-advisoryjoint-government-akira-advisory2026-09-02T13:42:01Zcomplete-sanitized
S03Microsoft Securityprimary-incident-responsemicrosoft2026-09-02T13:42:01Zcomplete-sanitized
S04MITRE ATT&CKauthoritative-knowledge-basemitre-attck2026-09-02T13:42:01Zcomplete-sanitized
S05Check Point Researchprimary-researchcheckpoint-research2026-09-02T13:42:01Zcomplete-sanitized

Claim ledger

ClaimStatementSourcesConfidenceContradiction / caveat
C01Mandiant observed REDBIKE (Akira) among ransomware operations targeting backup infrastructure, identity services, and virtualization management planes during 2025.S01highnone
C02M-Trends 2026 is based on more than 500,000 hours of Mandiant frontline incident investigations conducted globally during 2025.S01highnone
C03Akira has operated since at least March 2023 and is also tracked as Storm-1567, Howling Scorpius, Punk Spider, and Gold Sahara.S02, S04highnone
C04A June 2025 Akira incident encrypted Nutanix AHV virtual-machine disk files after abuse of CVE-2024-40766.S02highnone
C05Observed initial-access paths include VPN services without MFA, stolen or sprayed credentials, RDP, SSH, phishing, and exploitation of edge and backup-server vulnerabilities.S02, S04highnone
C06Akira actors have created domain accounts and used nltest, net commands, SoftPerfect, Advanced IP Scanner, and NetScan for domain and network discovery.S02highnone
C07Observed defense evasion includes terminating or uninstalling security tools and using AnyDesk, LogMeIn, PowerTool, and Impacket wmiexec.py.S02highnone
C08In one reported incident, actors powered down a domain-controller VM, copied its VMDK files, and extracted NTDS.dit and the SYSTEM hive from an attached copy.S02highnone
C09Observed lateral movement uses AnyDesk, LogMeIn, RDP, SSH, and MobaXterm.S02, S04highnone
C10Observed command-and-control and execution includes Ngrok tunneling plus PowerShell and WMIC for service disruption and script execution.S02highnone
C11Akira actors use WinRAR for staging and RClone, WinSCP, FileZilla, Ngrok, and other remote tooling for exfiltration; some incidents exfiltrated data just over two hours after access.S02, S04highnone
C12Akira uses double extortion, encrypts Windows and virtualization workloads, and inhibits recovery by deleting Windows volume shadow copies.S02, S04highnone
C13Current advisory artifacts include qKtul.vbs, s64.dll, w.exe, 1.bat, and akira.exe or win.exe with published SHA-256 values.S02highnone
C14Microsoft observed an attempted Akira attack in which a compromised domain controller initiated network encryption after broad secrets dumping and asset mapping.S03highnone
C15Check Point ranked Akira among four operations accounting together for 41 percent of Q1 2026 public data-leak-site victim claims.S05mediumpublic claims are not independently verified incidents
Evidence limits: Mandiant’s recovery-denial trend is broader than one fixed Akira playbook; Megazord is likely historical; public victim postings are not verified incidents; no public source proves every tool or technique occurs in every intrusion.
03

Hunt Brief and Attack Chain

The hunt model follows the operator from external access through identity and discovery, defensive impairment, staging and exfiltration, then recovery denial and encryption. It favors stable behavior and leaves platform-control gaps visible.

StepClaimsBehaviorPlatformDetection goal
1C05external access through vulnerable or weakly protected VPN, RDP, or SSH pathsnetworkidentify access-path telemetry and post-login anomalies
2C06, C08domain discovery, account creation, and credential acquisitionwindowsdetect discovery and high-risk identity manipulation
3C07, C09, C10security-control impairment, remote tooling, tunneling, and lateral movementcross-platformdetect pre-impact control evasion and durable remote access
4C11archive staging and rapid exfiltrationwindowscorrelate staging tools with transfer tooling
5C01, C04, C12, C14recovery inhibition and endpoint or virtualization-layer encryptioncross-platformidentify destructive commands and encryption fan-out before widespread impact

Hypotheses

IDBehaviorTelemetryUseLookbackValidation
H01execution of a known malicious artifactProcessRollup2hunt30d — balances low-volume hash matching with normal endpoint retentionuse a non-executing historical event fixture with a listed hash and a benign hash fixture; never run ransomware
H02domain and trust discoveryProcessRollup2hunt14d — discovery generally precedes impact by minutes to daysrun approved nltest discovery from a test workstation and compare with routine admin baselines
H03endpoint security impairmentProcessRollup2alert-candidate7d — destructive preparation is high-signal and time-sensitiveuse an approved benign service in a lab fixture to validate match and known maintenance commands to validate suppressions
H04encrypted protocol tunnelingProcessRollup2, NetworkConnectIP4hunt14d — tunnel tooling may persist through multiple operator sessionsexecute an approved tunnel client in a lab without exposing an internal service and compare with an allowlisted developer instance
H05archive staging followed by exfiltration toolingProcessRollup2hunt24h — supports short-interval staging and transfer correlationgenerate a benign archive and approved test transfer in a lab and compare with known backup and packaging hosts
H06volume shadow copy or backup recovery deletionProcessRollup2alert-candidate7d — destructive actions should be investigated promptlyuse a synthetic process-event fixture or an isolated disposable lab snapshot; do not remove production recovery data
H07domain-controller-led remote execution or encryption preparationProcessRollup2, NetworkConnectIP4hunt7d — domain-controller spread is high impact and time-sensitivereplay synthetic endpoint and network fixtures for a tagged lab domain controller, then compare with approved management fan-out
H08recovery-infrastructure and virtualization control-plane abusetenant-specific hypervisor, backup, and identity repositoriesgap30d — control-plane investigations often require longer retentionafter onboarding platform logs, replay documented administrative test actions and compare with maintenance windows

Affected surface and telemetry

Relevant surfaces are Windows endpoints and servers, Active Directory, externally reachable VPN and remote-access services, Veeam and other backup systems, domain controllers, VMware ESXi or Hyper-V, Nutanix AHV, and storage or cloud recovery planes. The portable CQL assumes Falcon process events and selected IPv4 context where populated. VPN authentication, identity changes, backup deletion, VM power and disk operations, hypervisor datastores, IPv6, proxy/DNS, and appliance events require tenant-specific repositories and field mapping.

04

Consolidated IOC Table

These five SHA-256 values come from the November 2025 joint advisory. They are detection and enrichment pivots, not independent authority for blocking or attribution.

IDTypeValueContextSourcesAction
I01sha256cf3465d7e49b609defa1e2b6cfcc86ffa30c72246cb2744dbf50736c5f3d74d5qKtul.vbs, VBScript used by Akira ransomwareS02detect
I02sha25658afef43cec0ee7a2fbfd9cdd5b71f55f971672d5e523a400b82b98c752ca5b7s64.dll backdoor reported in the updated advisoryS02detect
I03sha256bfd5fc6cd3dea74738ac7025fa14ea844f400708df2293572796568f65bd6b61w.exe encryptor reported in the updated advisoryS02detect
I04sha2568e12c8eb39cec9a414b56a36acbcc1a5b31dc96a38bc668138a00f94f7c26ea51.bat encryptor launcherS02detect
I05sha2567266e2afb5c70788c018d684698b0940eded4cb863f2b33f4edd31b59d1eab1dakira.exe or win.exe ransomware artifactS02detect
Context required: confirm file provenance, process lineage, host role, and source freshness before response. Common names such as w.exe are not useful without the matching hash.
05

ATT&CK Mapping

Rows marked direct preserve the joint advisory or MITRE mapping. Q07 uses an analyst-inferred umbrella mapping because its portable endpoint shape cannot prove which remote-service protocol originated the action.

TacticTechniqueNameBehaviorBasisSourcesClaims
Initial AccessT1078Valid Accountsactors abuse stolen external-access credentialsdirectS02, S04C05
DiscoveryT1018Remote System Discoverynetwork scanners and nltest enumerate reachable systems and domain controllersdirectS02, S04C06
Defense EvasionT1562.001Impair Defensesactors terminate or uninstall endpoint security toolingdirectS02C07
Lateral MovementT1021.001Remote Services: RDPactors use RDP after gaining accessdirectS02C09
Command and ControlT1572Protocol Tunnelingactors use Ngrok to create encrypted tunnelsdirectS02C10
CollectionT1560.001Archive Collected Data: Archive via Utilityactors use WinRAR before exfiltrationdirectS02, S04C11
ImpactT1490Inhibit System Recoveryencryptor invokes PowerShell to remove volume shadow copiesdirectS02C12
ImpactT1486Data Encrypted for Impactactors encrypt endpoint and virtualization storagedirectS02, S04C12
06

Native / Non-CQL Hunts

HuntLog sourceLogicResponse
Remote-access anomalyVPN or access-gateway sign-in console and authentication auditReview successful logins after password-spray or brute-force failures; compare MFA method, source, device, account privilege, and first-seen geography with approved access.Revoke sessions and reset only affected credentials after preservation and dependency review; patch the exposed access path.
New privileged identityWindows Security Event IDs 4720, 4728, 4732, 4756 and directory auditFind new accounts or additions to privileged groups, especially near VPN access, nltest discovery, remote tooling, or backup and hypervisor administration.Preserve directory changes and actor context; disable unauthorized accounts under identity-owner authority.
PowerShell recovery deletionMicrosoft-Windows-PowerShell/Operational Event ID 4104 and Windows process creationSearch script blocks for Win32_ShadowCopy, Remove-WmiObject, vssadmin, wbadmin, shadowcopy, or recovery-catalog deletion semantics.Preserve script blocks and process lineage; validate backup health and escalate unexplained destructive intent.
Backup and virtualization control planeVeeam audit, vCenter/ESXi tasks and events, Nutanix Prism/AHV audit, storage and cloud-backup activityReview unexpected VM power-off, VMDK or disk copy/attachment, datastore access, backup-object deletion, immutability changes, role changes, or privileged sessions.Freeze destructive jobs and constrain suspect identities only with platform-owner continuity approval; protect remaining recovery copies.
07

CrowdStrike LogScale CQL Hunt Queries

Pick your tenant's cloud first — every "Open in Falcon" button below uses this selection.
Query strategy: Q01, Q03, and Q06 are the strongest keepers. Q02 and Q07 expose useful pre-impact behavior with administrator overlap. Q04 and Q05 need same-host context and local allowlists. H08 remains a backup and virtualization log gap.

All queries are STATIC-ONLY. Confirm event presence and fields in a one-hour manual window, record parser results, then expand to the card lookback.

Q01 · Execution matching current Akira advisory hashes
CONF highFP lowCOST low

Looks for: process execution whose SHA-256 equals one of five current joint-advisory artifacts. Accomplishes: supplies the highest-confidence Akira pivot in the pack, while keeping response conditional on contextual verification rather than hash-only prevention.

Trace: H01 · Decision Q01

// HUNT: Akira advisory hash execution
// HYPOTHESIS: H01
// USE: hunt
// MITRE: T1486
// CONF: high
// FP: low
// COST: low
// TIMEFRAME: 30d — low-volume exact-hash retrospective
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; SHA256HashData, FileName, ImageFileName, CommandLine, aid, ComputerName, UserName, TargetProcessId, @timestamp
// FALSE POSITIVES: stale or incorrectly contextualized intelligence; no ordinary benign exact-hash match expected
// TUNING: Confirm source context and file provenance before containment; do not suppress exact matches solely by filename
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 2592000000)
| in(SHA256HashData, values=["cf3465d7e49b609defa1e2b6cfcc86ffa30c72246cb2744dbf50736c5f3d74d5","58afef43cec0ee7a2fbfd9cdd5b71f55f971672d5e523a400b82b98c752ca5b7","bfd5fc6cd3dea74738ac7025fa14ea844f400708df2293572796568f65bd6b61","8e12c8eb39cec9a414b56a36acbcc1a5b31dc96a38bc668138a00f94f7c26ea5","7266e2afb5c70788c018d684698b0940eded4cb863f2b33f4edd31b59d1eab1d"])
| table([@timestamp, aid, ComputerName, UserName, FileName, ImageFileName, CommandLine, SHA256HashData, TargetProcessId])
| sort(@timestamp, order=desc, limit=1000)
Q02 · Domain-controller and trust discovery commands
CONF mediumFP mediumCOST low

Looks for: nltest, net, or net1 commands that enumerate domain controllers or trust relationships. Accomplishes: catches a recurring pre-lateral-movement discovery step, but stays analyst-led because help-desk and domain administrators use the same utilities.

Trace: H02 · Decision Q02

// HUNT: Akira-style domain and trust discovery
// HYPOTHESIS: H02
// USE: hunt
// MITRE: T1482, T1018
// CONF: medium
// FP: medium
// COST: low
// TIMEFRAME: 14d — discovery commonly precedes impact by minutes to days
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; FileName, CommandLine, ParentBaseFileName, aid, ComputerName, UserName, @timestamp
// FALSE POSITIVES: domain administration, identity troubleshooting, deployment scripts
// TUNING: Exclude approved administrative accounts and known management hosts only after reviewing their exact commands
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 1209600000)
| FileName = /^(?:nltest|net|net1)(?:\.exe)?$/i
| CommandLine = /(?:\/dclist:|\/domain_trusts|domain trust|domain_controller)/i
| groupBy([aid, ComputerName, UserName, FileName, ParentBaseFileName, CommandLine], function=[count(as=Executions), min(@timestamp, as=FirstSeen), max(@timestamp, as=LastSeen)], limit=1000)
| sort(LastSeen, order=desc, limit=1000)
Q03 · Commands that impair security or recovery services
CONF highFP mediumCOST medium

Looks for: command interpreters and service tools issuing stop, delete, disable, uninstall, or kill actions against endpoint security, backup, or recovery components. Accomplishes: targets the pre-impact defense-evasion boundary with actionable host and user context.

Trace: H03 · A01

// HUNT: Security-control impairment before ransomware impact
// HYPOTHESIS: H03
// USE: alert-candidate
// MITRE: T1562.001
// CONF: high
// FP: medium
// COST: medium
// TIMEFRAME: 7d — high-risk preparation requires prompt review
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; FileName, CommandLine, ParentBaseFileName, aid, ComputerName, UserName, @timestamp
// FALSE POSITIVES: authorized security-agent maintenance, upgrades, and incident-response containment
// TUNING: Exclude only approved maintenance account, host, parent, and command combinations with change-window evidence
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 604800000)
| FileName = /^(?:powershell|pwsh|cmd|sc|net|net1|taskkill|wmic|msiexec)(?:\.exe)?$/i
| CommandLine = /(?:stop|delete|disable|uninstall|remove|terminate|taskkill).{0,100}(?:defender|crowdstrike|falcon|sentinel|carbonblack|sophos|trend|mcafee|veeam|backup|antivirus|endpoint|edr|vss)/i
| table([@timestamp, aid, ComputerName, UserName, ParentBaseFileName, FileName, CommandLine])
| sort(@timestamp, order=desc, limit=1000)
Q04 · Tunnel and remote-access client execution
CONF mediumFP highCOST medium

Looks for: Ngrok, Cloudflare Tunnel, RustDesk, AnyDesk, LogMeIn, or MobaXterm execution with tunnel or remote-session arguments. Accomplishes: surfaces operator access and C2 tooling, but needs same-host network context and a local approval inventory.

Trace: H04 · Decision Q04

// HUNT: Akira-associated tunnel and remote-access tooling
// HYPOTHESIS: H04
// USE: hunt
// MITRE: T1572, T1219
// CONF: medium
// FP: high
// COST: medium
// TIMEFRAME: 14d — remote tooling may persist across several operator sessions
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; FileName, ImageFileName, CommandLine, ParentBaseFileName, aid, ComputerName, UserName, TargetProcessId, @timestamp
// FALSE POSITIVES: approved developer tunnels, remote support, and administrator troubleshooting
// TUNING: Exclude owner-approved binary hash, signer, account, host group, and command pattern combinations
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 1209600000)
| FileName = /^(?:ngrok|cloudflared|rustdesk|anydesk|logmein|mobaxterm)(?:\.exe)?$/i
| CommandLine = /(?:tcp|http|tunnel|connect|service|server|relay|remote|access)/i
| table([@timestamp, aid, ComputerName, UserName, ParentBaseFileName, FileName, ImageFileName, CommandLine, SHA256HashData, TargetProcessId])
| sort(@timestamp, order=desc, limit=1000)
Q05 · Archive and transfer tools on the same host
CONF mediumFP highCOST medium

Looks for: an archive utility and an exfiltration-capable transfer client appearing on one endpoint during 24 hours. Accomplishes: highlights the staging-to-exfiltration handoff, while deliberately requiring timeline review because backup and migration jobs can look identical.

Trace: H05 · Decision Q05

// HUNT: Same-host archive staging and transfer tooling
// HYPOTHESIS: H05
// USE: hunt
// MITRE: T1560.001, T1567.002
// CONF: medium
// FP: high
// COST: medium
// TIMEFRAME: 24h — bounds same-host staging and transfer correlation
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; FileName, CommandLine, aid, ComputerName, UserName, @timestamp
// FALSE POSITIVES: backup jobs, software packaging, migration work, and administrator file transfers
// TUNING: Exclude approved backup and migration hosts plus service accounts; then require unusual archive paths or destinations
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 86400000)
| FileName = /^(?:rar|winrar|7z|tar|rclone|winscp|winscpnet|filezilla)(?:\.exe)?$/i
| selfJoinFilter(field=[aid], where=[{FileName = /^(?:rar|winrar|7z|tar)(?:\.exe)?$/i}, {FileName = /^(?:rclone|winscp|winscpnet|filezilla)(?:\.exe)?$/i}])
| groupBy([aid, ComputerName], function=[count(as=Executions), collect(FileName, limit=20), collect(UserName, limit=20), min(@timestamp, as=FirstSeen), max(@timestamp, as=LastSeen)], limit=1000)
| sort(LastSeen, order=desc, limit=1000)
Q06 · Shadow-copy and recovery deletion commands
CONF highFP mediumCOST low

Looks for: vssadmin, WMIC, PowerShell, or wbadmin commands that delete shadow copies, recovery catalogs, or system-state backups. Accomplishes: catches a durable ransomware impact precursor that warrants urgent review and careful maintenance-window suppression.

Trace: H06 · A02

// HUNT: Recovery inhibition through shadow-copy or catalog deletion
// HYPOTHESIS: H06
// USE: alert-candidate
// MITRE: T1490
// CONF: high
// FP: medium
// COST: low
// TIMEFRAME: 7d — destructive actions require prompt review
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; FileName, CommandLine, ParentBaseFileName, aid, ComputerName, UserName, @timestamp
// FALSE POSITIVES: approved backup maintenance, gold-image preparation, and storage cleanup
// TUNING: Exclude only documented maintenance accounts, hosts, and exact command patterns within approved windows
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 604800000)
| FileName = /^(?:vssadmin|wmic|powershell|pwsh|wbadmin)(?:\.exe)?$/i
| CommandLine = /(?:delete|remove).{0,80}(?:shadowcopy|shadows|catalog|systemstatebackup)|(?:shadowcopy|shadows|catalog|systemstatebackup).{0,80}(?:delete|remove)/i
| table([@timestamp, aid, ComputerName, UserName, ParentBaseFileName, FileName, CommandLine])
| sort(@timestamp, order=desc, limit=1000)
Q07 · Remote-execution tooling on critical servers
CONF mediumFP highCOST medium

Looks for: PsExec, WMI, service-control, or remote-shell command patterns associated with lateral execution. Accomplishes: provides a domain-controller spreader pivot when restricted to known critical servers, but is intentionally hunt-only until asset role and fan-out are validated.

Trace: H07 · Decision Q07

// HUNT: Remote execution from potential ransomware spreaders
// HYPOTHESIS: H07
// USE: hunt
// MITRE: T1021
// CONF: medium
// FP: high
// COST: medium
// TIMEFRAME: 7d — high-impact lateral movement requires prompt scoping
// REQUIRES: Falcon endpoint event repository; ProcessRollup2; FileName, CommandLine, ParentBaseFileName, aid, ComputerName, UserName, @timestamp; tenant critical-server or domain-controller host context
// FALSE POSITIVES: software deployment, domain administration, backup orchestration, and vulnerability scanning
// TUNING: Restrict to verified domain controllers or critical servers and exclude approved management parents, accounts, and command patterns
// VALIDATION: STATIC-ONLY
#event_simpleName = ProcessRollup2
| test(@timestamp >= now() - 604800000)
| (FileName = /^(?:psexec|psexesvc|wmic|sc|winrs)(?:\.exe)?$/i or CommandLine = /(?:wmiexec\.py|\/node:|sc\.exe \\|winrs -r:|psexec)/i)
| table([@timestamp, aid, ComputerName, UserName, ParentBaseFileName, FileName, ImageFileName, CommandLine])
| sort(@timestamp, order=desc, limit=1000)
08

Operationalization and IOA Candidates

Q03 and Q06 have complete scheduled-search designs, but both remain DESIGN ONLY. The other five queries remain hunt-only. No schedule, notification, prevention, or containment action was created.

QueryUseDecisionAlertReadinessRationale
Q01hunthunt-onlydesign-onlyExact hashes are high-confidence pivots, but static source context does not establish freshness, tenant parsing, or an approved response workflow.
Q02hunthunt-onlydesign-onlyDomain discovery has substantial legitimate administrator overlap and needs tenant baseline and account/host exclusions.
Q03alert-candidatealert-packageA01design-onlyDefense impairment has stable host and command semantics and a plausible maintenance-window suppression model, but tenant parse and canary evidence are absent.
Q04hunthunt-onlydesign-onlyRemote-support and tunneling tools are common enough to require an approved-software inventory and same-host network review.
Q05hunthunt-onlydesign-onlyThe same-host archive and transfer sequence is useful for hunting but is not temporally ordered and overlaps backup and migration workflows.
Q06alert-candidatealert-packageA02design-onlyRecovery deletion has stable host and command semantics and warrants urgent review, but tenant parsing and benign maintenance baselines are absent.
Q07hunthunt-onlydesign-onlyThe portable query lacks reliable domain-controller role and fan-out context, so result semantics are not stable enough for scheduling.

Design-only scheduled searches

IDQueryNameWindow / cadenceThresholdSuppressionOwner / SLA
A01Q03Security Control Impairment Command30m / 15mone matching process event30 minutes for identical dedupe key; never suppress a new host, user, command line, or maintenance-window violationdetection engineering with SOC response ownership / triage within 15 minutes
A02Q06Recovery Artifact Deletion Command30m / 15mone matching process event30 minutes for identical dedupe key; never suppress a new host, user, command line, or execution outside an approved maintenance windowdetection engineering with incident response ownership / triage within 10 minutes

IOA01 · detect-only candidate

Source: Q06 / H06. Match recovery-management utilities plus destructive shadow-copy or catalog arguments. Pilot only in detect mode on disposable lab systems, test approved maintenance, measure benign volume, obtain endpoint and incident-response approval, and retain a one-step disable rollback. Static design never authorizes block mode.

09

Machine-Readable IOC Appendix

Copy blocks retain source and indicator linkage. Hash matches support detection and enrichment only; filenames, extensions, and notes are lower-fidelity pivots that need path, timing, lineage, and file-content context.

SHA-256 CSV5 values
type,value,action,severity,expiration,description,tags
sha256,cf3465d7e49b609defa1e2b6cfcc86ffa30c72246cb2744dbf50736c5f3d74d5,detect,high,2027-09-02,qKtul.vbs; VBScript used by Akira ransomware I01,source:S02
sha256,58afef43cec0ee7a2fbfd9cdd5b71f55f971672d5e523a400b82b98c752ca5b7,detect,high,2027-09-02,s64.dll backdoor reported in the updated advisory I02,source:S02
sha256,bfd5fc6cd3dea74738ac7025fa14ea844f400708df2293572796568f65bd6b61,detect,high,2027-09-02,w.exe encryptor reported in the updated advisory I03,source:S02
sha256,8e12c8eb39cec9a414b56a36acbcc1a5b31dc96a38bc668138a00f94f7c26ea5,detect,high,2027-09-02,1.bat encryptor launcher I04,source:S02
sha256,7266e2afb5c70788c018d684698b0940eded4cb863f2b33f4edd31b59d1eab1d,detect,high,2027-09-02,akira.exe or win.exe ransomware artifact I05,source:S02
Filename pivots5 names
qKtul.vbs | I01 | S02
s64.dll | I02 | S02
w.exe | I03 | S02
1.bat | I04 | S02
akira.exe or win.exe | I05 | S02
Impact artifacts6 values
.akira | encrypted extension | S02
.powerranges | encrypted extension | S02
.akiranew | encrypted extension | S02
.aki | encrypted extension | S02
akira_readme.txt | ransom note | S02
akiranew.txt | ransom note | S02
Do not block by filename or extension alone: several names are generic and may be imitated. Use Q01 for exact hash context and preserve the file for verification.
10

Hardening — Tiered and Deployable

Immediate — preserve access and recovery options
  • Require phishing-resistant MFA for VPN, remote access, and privileged administration (M1032; CTRL01) — Set each remote-access identity policy to require a phishing-resistant factor for all privileged and external sessions; remove single-factor exceptions; constrain emergency accounts to monitored break-glass use. deployable-design Verify: review effective sign-in policy and complete one allowed phishing-resistant login plus one denied password-only login Expected: phishing-resistant session succeeds; password-only session is denied; audit record identifies policy Rollback: restore the previous versioned access policy only under identity-owner approval, keep emergency monitoring enabled, and document the temporary exception Authority: S02 · AA24-109A, updated 2025-11-13.
  • Protect independent offline or immutable recovery copies and prove restoration (M1053; CTRL02) — Maintain at least one recovery copy that production and domain administrators cannot alter or delete; enable platform immutability or offline media where supported; schedule a representative restore test and record recovery time and integrity. deployable-design Verify: use read-only policy inspection and restore a representative copy to an isolated target Expected: production administrators cannot delete the protected copy and restored data passes integrity and application checks Rollback: do not shorten an active retention lock; for reversible policy changes, restore the prior version only after recovery and legal-owner approval Authority: S02 · AA24-109A, updated 2025-11-13.
  • Pilot ransomware and PsExec/WMI Attack Surface Reduction rules in audit mode (M1040; CTRL03) — Deploy both rules with action AuditMode to a test ring, measure legitimate hits, create narrow exclusions, then use change control before moving a second ring to Enabled. deployable-design Verify: run Get-MpPreference and inspect Defender Operational events for both rule GUIDs Expected: both GUIDs show AuditMode in the pilot and test activity records audit events Rollback: set the two pilot rules to Disabled or restore the previous versioned Defender policy, then verify their effective action Authority: https://learn.microsoft.com/en-us/defender-endpoint/attack-surface-reduction-rules-reference · Microsoft ASR rules reference, accessed 2026-09-02.
Near-term — constrain operator movement and administration
  • Allowlist remote-management and tunneling tools by approved identity, host, hash, and destination (M1037; CTRL04) — Create an approved-tool register and block or remove unapproved instances; constrain approved tools to named support accounts, managed hosts, signed or hashed binaries, and documented destinations; alert on deviations. deployable-design Verify: compare installed/running tool inventory and egress events against the approved register Expected: only approved combinations execute and connect; a benign unapproved fixture is blocked or alerted Rollback: restore the prior application or egress policy for the pilot group and retain alert-only monitoring while exceptions are corrected Authority: S02 · AA24-109A, updated 2025-11-13.
  • Separate recovery and hypervisor administration from routine domain administration (M1030; CTRL05) — Use distinct privileged identities and management workstations for identity, backup, and virtualization tiers; deny routine domain-admin access to backup and hypervisor consoles; restrict management traffic through dedicated segments or jump hosts. deployable-design Verify: review effective role assignments and network rules, then test one authorized and one unauthorized administrative path Expected: tier-specific admin succeeds; routine domain-admin path is denied and logged Rollback: restore the previous role or network rule set from version control for the pilot only, verify recovery jobs, and keep enhanced monitoring active Authority: S02 · AA24-109A, updated 2025-11-13.
Strategic — expose recovery-plane abuse
  • Centralize tamper-resistant hypervisor, backup, identity, and storage audit logs (M1047; CTRL06) — Forward administrative, authentication, object-deletion, VM power, virtual-disk, datastore, backup-job, and policy-change logs to a separately administered central repository with retention long enough for incident scoping. deployable-design Verify: perform documented read-only login and non-destructive test change, then verify arrival, parsing, timestamps, and retention in the central repository Expected: every test action appears with actor, target, source, outcome, and timestamp Rollback: disable the pilot forwarder or collector configuration, restore the prior logging settings, and preserve already ingested records Authority: S01 · M-Trends 2026, 2026-03-23.

Deployable playbook · PB01 · Audit-first ASR pilot for ransomware and PsExec/WMI behavior

  1. Confirm Defender ASR support, central management ownership, pilot hosts, and policy rollback path; export the current Defender policy.
  2. Capture Get-MpPreference output and relevant Defender Operational events before change.
  3. On the pilot only, set C1DB55AB-C21A-4637-BB3F-A12568109D35 and D1E49AAC-8F56-4280-B9BA-993A6D77406C to AuditMode through the managed policy channel.
  4. Verify both GUIDs are effective and generate only approved benign test activity; expected result is an audit event with host, rule GUID, and process context.
  5. Confirm application, deployment, backup, and remote administration health.
  6. Expand only after a documented benign baseline and narrow exclusions are approved; block mode requires separate change approval.
  7. Rollback by restoring the prior versioned policy or setting the two pilot actions to Disabled; verify effective state and application health.
  8. Retain policy exports, command output, audit events, exclusions, health checks, owner, and approval record.

Deployable playbook · PB02 · Protected recovery-copy and restore proof

  1. Identify a noncritical workload, its recovery owner, isolated restore target, legal retention constraints, and current recovery-policy export.
  2. Capture current backup-copy locations, administrator roles, retention or immutability state, and most recent restore evidence.
  3. Create or designate an independent protected copy and remove production or domain administrator delete authority in the pilot.
  4. Attempt a read-only policy check and an authorized isolated restore; expected result is denied deletion by the production administrator and a usable restored workload.
  5. Confirm production backup jobs and restore service remain healthy.
  6. Expand only after recovery time, integrity, cost, and legal retention are accepted by service and recovery owners.
  7. Do not attempt to shorten an active retention lock; for reversible access-policy changes, restore only the prior pilot roles after approval and verify access and backup health.
  8. Retain policy exports, denial evidence, restore logs, integrity results, owner, and approval record.
Design state: no hardening change is canary-tested or deployed. Product version, topology, dependencies, continuity, and approval must be checked before execution.
11

Containment Runbook

PhaseTriggerAuthorityOwnerEvidenceRecovery
Validateone high-confidence hit or correlated medium-confidence behaviorsSOC leadSOC analystraw events, process tree, user, host role, hash, source contextno service change; close only with documented benign explanation
Contain endpointconfirmed unauthorized defense impairment, recovery deletion, known hash, or encryption preparationincident commanderendpoint responsevolatile process/network state, files, memory decision, sensor statusisolate affected endpoint while preserving management access; release only after rebuild or validated remediation
Constrain identitystolen credential, new privileged account, abnormal remote access, or DC spread evidenceincident commander plus identity owneridentity responsesign-in logs, group changes, sessions, credential-use timelinerevoke sessions and rotate affected credentials in dependency order; preserve break-glass and service continuity
Protect recovery planesbackup deletion, VM power/disk manipulation, or hypervisor administrative anomalyincident commander plus platform ownerbackup and virtualization responsemanagement audit logs, role exports, object and job history, storage eventsfreeze destructive jobs and restrict suspect identities without powering down critical infrastructure unless continuity is approved
Scope and eradicatecontainment stabilized and evidence preservedincident commanderincident response with platform ownersenvironment-wide hash and behavior hunts, persistence review, vulnerability and credential scopepatch access paths, remove unauthorized tools/accounts, rebuild affected systems, and validate protected backups
Restore and monitoreradication evidence complete and recovery copy validatedrecovery lead and business ownerservice recoveryrestore logs, integrity tests, control verification, post-restore telemetryrestore in priority order; re-hunt at 24 hours, 72 hours, and 7 days

Preservation order: alert and query results; raw endpoint, identity, VPN, backup, hypervisor, storage, network, and DNS events; process tree and command line; files and hashes; network sessions; identity state; recovery-plane configurations; analyst notes and tool logs.

Continuity exception: Do not isolate domain controllers, backup controllers, hypervisors, storage controllers, or shared network infrastructure without platform-owner continuity approval unless active destructive impact leaves no safer option.

Closure: close the access path, remediate affected identities in dependency order, verify recovery controls and restored services, retain decisions, and re-hunt at 24 hours, 72 hours, and seven days.

12

Detection Coverage and Validation Evidence

Validation state: STATIC REVIEW PASSED after local structure/safety, maintained-field, CQL heuristic, and IOC provenance gates. Falcon tenant execution has not been performed. No parser result, positive test, benign test, scheduled run, IOA detection, or prevention evidence exists.

Technique / behaviorCoverageQuery / handoffEvidenceLimitation
T1078GapNative VPN/identity huntDesignExternal authentication schema not mapped
T1482 / T1018StaticQ02Local structural and heuristic reviewAdministrator baseline and tenant parsing absent
T1562.001StaticQ03 / A01Local structural and heuristic reviewMaintenance baseline and canary absent
T1021StaticQ07Local structural and heuristic reviewCritical-server role and fan-out context absent
T1572 / T1219StaticQ04Local structural and heuristic reviewApproved-tool inventory and network confirmation absent
T1560.001 / T1567.002StaticQ05Local structural and heuristic reviewOrdering, destinations, and benign baseline absent
T1490StaticQ06 / A02 / IOA01Local structural and heuristic reviewTenant parse, positive test, and benign baseline absent
T1486StaticQ01 plus Q03/Q06 precursorsLocal structural and heuristic reviewExact hashes are brittle; encryption outcome not directly measured
T1490 management planeGapH08Named telemetry designBackup, VMware, Nutanix, storage, and cloud schemas absent

Recorded validation evidence and next tests

  • Seven queries were reviewed only by local static tooling; each keeps VALIDATION: STATIC-ONLY.
  • Q03 and Q06 remain design-only alert candidates; observed baseline is unknown and safe positive and benign tests are planned but not run.
  • Q05 identifies co-occurrence within a day and does not prove ordering; Q07 needs asset role and fan-out context; Q04 needs network confirmation.
  • H08 requires management-plane log onboarding and field mapping; VPN access, IPv6, proxy/DNS, Linux, ESXi, and Nutanix coverage are not assumed.
  • Next step: parse-check Q01, Q03, and Q06 in the intended Falcon repository using a one-hour window, record field population and result semantics, then replay safe fixtures before considering canary scheduling.
13

Hunt Summary Ticket

TITLE:        Akira / REDBIKE ransomware hunt — v0.3 Draft
SEVERITY:     critical — recovery denial can combine identity, backup, and virtualization compromise with encryption
SCOPE:        Windows process and IPv4 endpoint telemetry; VPN, identity, backup, VMware, Nutanix, storage, and cloud audit pivots
HYPOTHESIS:   H01 exact hashes; H02 domain discovery; H03 defense impairment; H04 tunnels/RMM; H05 staging and transfer; H06 recovery deletion; H07 critical-server spread; H08 recovery-plane gap
QUERIES RUN:  inventory: none; hunt: Q01/Q02/Q04/Q05/Q07; alert-candidate: Q03/Q06
DO FIRST:     Q03 and Q06 over 7 days, then correlate hits with Q01 and Q07
FINDINGS:
GAPS:         tenant parsing absent; H08 control-plane schemas; VPN, identity, IPv6, proxy/DNS, Linux/ESXi, and Nutanix coverage not mapped
ACTIONS:      SOC validates Q01/Q03/Q06; recovery owners protect backups; platform owners centralize and review management-plane logs
OWNER:        security operations with identity, endpoint, backup, virtualization, and network owners
VERSION:      v0.3 Draft · 2026-09-04 · STATIC REVIEW PASSED
14

Changelog

v0.3 Rich visual emphasis2026-09-04Added coordinated semantic color to Executive Summary lead-ins, threat metadata, Severity, and IOC counts. Detection logic, evidence, indicators, hardening, and validation claims are unchanged.
v0.2 Theme refresh2026-09-04Applied the deterministic threat-aware HuntPack palette. Detection logic, evidence, indicators, hardening, and validation claims are unchanged.
v0.1 Draft2026-09-02Initial Akira / REDBIKE HuntPack using M-Trends 2026, the November 2025 joint advisory, Microsoft incident-response reporting, MITRE ATT&CK, and Q1 2026 research. Includes seven CQL designs, five advisory hashes, two design-only alerts, one detect-only IOA candidate, six controls, two playbooks, and a six-phase runbook.
15

References

IDPublisherVersion / statusAccessedUseURL
S01Google Cloud / Mandiantcomplete-sanitized2026-09-02T13:42:01ZM-Trends 2026 recovery-denial framing and telemetry guidancehttps://cloud.google.com/blog/topics/threat-intelligence/m-trends-2026
S02FBI, CISA, DC3, HHS and international partnerscomplete-sanitized2026-09-02T13:42:01ZAkira TTPs, IOCs, aliases, affected surfaces, and mitigationshttps://www.ic3.gov/CSA/2025/251113.pdf
S03Microsoft Securitycomplete-sanitized2026-09-02T13:42:01ZDomain-controller spreader case and pre-encryption behaviorhttps://www.microsoft.com/en-us/security/blog/2025/04/09/how-cyberattackers-exploit-domain-controllers-using-ransomware/
S04MITRE ATT&CKcomplete-sanitized2026-09-02T13:42:01ZActor aliases, activity timeline, and ATT&CK technique contexthttps://attack.mitre.org/groups/G1024/
S05Check Point Researchcomplete-sanitized2026-09-02T13:42:01ZQ1 2026 activity context with public-claim caveathttps://research.checkpoint.com/2026/the-state-of-ransomware-q1-2026/
AUTH01MicrosoftASR rules reference, accessed 2026-09-022026-09-02CTRL03 rule GUIDs, audit-first deployment, and rollbackhttps://learn.microsoft.com/en-us/defender-endpoint/attack-surface-reduction-rules-reference