Data Encrypted for Impact — Ransomware Pre-Deployment Staging Indicators
The hours before ransomware deployment follow a repeatable pattern regardless of group: network share enumeration, credential dumping, detection tool impairment, and staging of the ransomware binary in accessible locations. NCSC UK 2025 threat report identified Akira, Black Basta, and Play as the most active ransomware groups targeting UK SMBs. The staging sequence typically occurs within 1-48 hours before encryption begins, offering a detection opportunity. Key indicators: (1) net use or net share enumeration across the network; (2) vssadmin.exe or wmic delete shadowstorage (shadow copy deletion — the final indicator before encryption); (3) remote execution tool setup (PsExec, PAExec, WMI, WinRM) preparing for domain-wide payload deployment; (4) large file transfers or staging directories created; (5) AV/EDR impairment attempts. This detection targets the staging window before encryption — detection here prevents the actual ransomware event.
What is THREAT-Ransomware-StagingIndicators Ransomware Pre-Deployment Staging Indicators?
Ransomware Pre-Deployment Staging Indicators (THREAT-Ransomware-StagingIndicators) is a sub-technique of Data Encrypted for Impact (T1486) in the MITRE ATT&CK framework. It maps to the Impact and Discovery and Lateral Movement tactics — the adversary is trying to manipulate, interrupt, or destroy your systems and data.
This page provides production-ready detection logic for Ransomware Pre-Deployment Staging Indicators, covering the data sources and telemetry it touches: Microsoft Defender for Endpoint (DeviceProcessEvents), Sysmon, Windows Security Event Log. The queries below are rated critical severity at high confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Impact Discovery Lateral Movement
// THREAT: Ransomware Pre-Deployment Staging Indicators
// Detects the staging sequence used by Akira, Black Basta, LockBit, Play
// before mass ransomware deployment across the domain
// Indicator 1: Shadow copy deletion (T1490 — immediate escalation)
let ShadowDelete = DeviceProcessEvents
| where Timestamp > ago(24h)
| where (
(FileName =~ "vssadmin.exe" and ProcessCommandLine has_any ("delete", "resize", "shadowstorage"))
or (FileName =~ "wmic.exe" and ProcessCommandLine has_any ("shadowcopy", "delete", "shadow"))
or (FileName =~ "powershell.exe" and ProcessCommandLine has_any ("Delete-ShadowCopy", "Win32_ShadowCopy", "vssadmin"))
or (FileName =~ "bcdedit.exe" and ProcessCommandLine has_any ("recoveryenabled", "no", "bootstatuspolicy", "ignoreallfailures"))
)
| extend StageIndicator = "ShadowCopyDeletion"
| extend StagingRisk = 100;
// Indicator 2: Network share enumeration (mass reconnaissance)
let ShareEnum = DeviceProcessEvents
| where Timestamp > ago(24h)
| where (
(FileName =~ "net.exe" and ProcessCommandLine has_any ("view", "share", "use"))
or (FileName =~ "net1.exe" and ProcessCommandLine has_any ("view", "share"))
or (FileName =~ "netscan.exe")
or (FileName =~ "AdFind.exe")
or (FileName =~ "nltest.exe" and ProcessCommandLine has_any ("dclist", "domain_trusts", "server", "all_trusts"))
)
| summarize EnumCount=count() by DeviceName, AccountName, bin(Timestamp, 15m)
| where EnumCount >= 5
| extend StageIndicator = "NetworkShareEnumeration"
| extend StagingRisk = 70;
// Indicator 3: Remote execution tools for mass deployment
let RemoteExec = DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("psexec.exe", "psexec64.exe", "paexec.exe", "remcom.exe")
or (FileName =~ "wmic.exe" and ProcessCommandLine has "/node:" and ProcessCommandLine has "process call create")
or (FileName =~ "powershell.exe" and ProcessCommandLine has_any ("Invoke-WMIMethod", "Invoke-Command", "New-PSSession")
and ProcessCommandLine has_any ("-ComputerName", "-cn") and DeviceName != AccountDomain)
| extend StageIndicator = "RemoteExecutionToolUsed"
| extend StagingRisk = 80;
// Indicator 4: AV/EDR impairment (T1562.001)
let DefenseImpair = DeviceProcessEvents
| where Timestamp > ago(24h)
| where (
(FileName =~ "sc.exe" and ProcessCommandLine has_any ("stop", "delete", "config") and
ProcessCommandLine has_any ("WinDefend", "Sense", "MpsSvc", "wscsvc", "WdFilter", "WdNisSvc",
"SecurityHealthService", "SentinelAgent", "CSFalconService"))
or (FileName =~ "taskkill.exe" and ProcessCommandLine has_any (
"msmpeng", "mssense", "csagent", "sentinelagent", "cbdaemon", "mbam"))
or (FileName =~ "reg.exe" and ProcessCommandLine has_any ("add", "delete") and
ProcessCommandLine has_any ("WinDefend", "DisableAntiSpyware", "DisableRealtimeMonitoring",
"SOFTWARE\\Policies\\Microsoft\\Windows Defender"))
)
| extend StageIndicator = "DefenseImpairmentAttempt"
| extend StagingRisk = 90;
union ShadowDelete, RemoteExec, DefenseImpair
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine,
InitiatingProcessFileName, StageIndicator, StagingRisk
| sort by StagingRisk desc, Timestamp desc Multi-indicator ransomware staging detection targeting the 1-48 hour pre-encryption window. Detects four key staging activities: shadow copy deletion (immediate escalation — encryption is imminent), network share enumeration (reconnaissance for deployment targets), remote execution tool setup (PsExec, WMI remoting for mass deployment), and AV/EDR impairment. StagingRisk score (70-100) indicates proximity to active ransomware deployment.
Data Sources
Required Tables
False Positives
- Legitimate IT backup tools (Veeam, Acronis, Backup Exec) that use vssadmin to manage shadow copies
- System administrators using net view/net share for legitimate inventory
- PsExec used by IT staff for remote administration or software deployment during maintenance windows
- Endpoint management platforms (SCCM, Qualys, Tanium) that invoke WMI remote execution for patch deployment
- Security testing by authorised penetration testers (shadow copy deletion should be excluded from scope)
Sigma rule & cross-platform mapping
The detection logic for Ransomware Pre-Deployment Staging Indicators (THREAT-Ransomware-StagingIndicators) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: process_creation
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for THREAT-Ransomware-StagingIndicators
Testing Methodology
Validate this detection against 2 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Shadow Copy Deletion via vssadmin (Ransomware Staging Simulation)
Expected signal: Sysmon Event ID 1: vssadmin.exe process creation with 'delete shadows' in command line. Security Event ID 4688 if command line auditing enabled.
- Test 2Windows Defender Disable via PowerShell
Expected signal: Sysmon Event ID 1: powershell.exe with DisableRealtimeMonitoring in command line. Windows Defender event log records protection disabled.
Response Playbook
Triage
- Shadow copy deletion is a near-certain ransomware precursor — if vssadmin delete or wmic shadowcopy delete is detected, trigger incident response immediately without waiting for additional confirmation.
- Identify the user and process context: is this a service account, a domain admin, or a standard user? Ransomware staging almost always involves elevated privileges. Check how those privileges were obtained.
- Map the affected hosts: are multiple hosts showing staging indicators simultaneously? Multi-host staging indicates the attacker has already achieved domain compromise and is preparing for a domain-wide deployment.
- Check for PsExec or PAExec: the presence of these tools in unusual locations (C:\Users\, C:\ProgramData\, C:\Windows\Temp\) is a ransomware staging indicator even without shadow copy deletion.
- Review network traffic from affected hosts for bulk file access (the attacker may also be exfiltrating data before encryption — double extortion).
Containment
- Isolate affected endpoints via EDR host isolation immediately upon shadow copy deletion detection. Do not wait — encryption may begin within minutes.
- Block lateral movement: disable RDP, SMB, and WinRM to non-management hosts at the firewall if domain-wide staging is detected.
- Preserve shadow copies on unaffected systems immediately: run vssadmin create shadow /for=C: on all critical servers that haven't been affected.
- Force-disable any identified compromised accounts (domain admin accounts used for staging).
- Take offline backups: if you have offline/immutable backups, verify their integrity immediately and isolate backup infrastructure from the network.
Evidence Collection
- Process creation logs (Sysmon Event ID 1 or Security 4688) for all staging binaries
- Network file access logs: which shares were accessed, how many files, what size
- Authentication logs: which account(s) were used for PsExec/WMI remote execution
- EDR timeline for affected hosts: full process tree, file writes, network connections in 48h window before staging
- Active Directory logs: any privilege escalation or new account creation preceding staging
Escalation Criteria
- ! Shadow copy deletion detected on any host — immediate incident declaration
- ! PsExec or PAExec executed from unusual locations by unusual accounts
- ! AV/EDR impairment attempts affecting multiple hosts
- ! Staging indicators across 5+ hosts simultaneously — indicates domain-wide deployment preparation
- ! Data staging directories created with large file counts (exfiltration before encryption)
Investigation Guide
Forensic Artifacts
- >
Sysmon Event ID 1 process creation for vssadmin, wmic, psexec, sc, taskkill - >
Windows Event ID 7040 (service disabled) for AV/EDR service impairment - >
File system: presence of staging binaries (psexec.exe, paexec.exe) in temp directories - >
Registry: HKLM\SOFTWARE\Policies\Microsoft\Windows Defender for Group Policy-level AV disablement - >
Network shares: SMB access logs showing bulk file reads from domain controller or file server (exfiltration)
Tuning Guidance
Shadow copy deletion is almost never a legitimate user action — the only expected sources are backup software service accounts (Veeam, Acronis, Windows Backup service). Create an exclusion list for those specific service account names and parent process names (e.g., VeeamBackupSvc, BackupExec). For PsExec, create allowlist exceptions for known IT admin accounts. The AV/EDR impairment detection has more potential for false positives from legitimate security tool upgrades — add exclusions for vendor-specific processes (CrowdStrike, Defender update processes). The key is treating shadow copy deletion as an immediate incident trigger, not a standard alert.
Hunting Queries
Hunt for shadow copy and backup deletion commands across the environment — any occurrence is high-priority given lack of legitimate use cases for these specific command patterns outside of authorised backup tooling.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FileName in~ ("vssadmin.exe", "wmic.exe", "bcdedit.exe")
and ProcessCommandLine has_any ("delete", "shadowcopy", "shadow", "recoveryenabled")
| summarize Count=count(), Hosts=make_set(DeviceName)
by FileName, ProcessCommandLine
| sort by Count desc index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
(Image="*\\vssadmin.exe" OR Image="*\\wmic.exe" OR Image="*\\bcdedit.exe")
(CommandLine="*delete*" OR CommandLine="*shadow*" OR CommandLine="*recoveryenabled*")
| stats count AS Hits, dc(host) AS HostCount, values(host) AS Hosts
BY Image, CommandLine
| sort - Hits Atomic Red Team Tests
Deletes volume shadow copies using vssadmin — the most common ransomware staging indicator. This should be run in a sandbox environment only.
Command
vssadmin delete shadows /all /quiet Expected Telemetry
Sysmon Event ID 1: vssadmin.exe process creation with 'delete shadows' in command line. Security Event ID 4688 if command line auditing enabled.
Expected Detection
Alert fires on ShadowCopyDeletion indicator with RiskScore=100. Immediate escalation required.
Disables Windows Defender real-time monitoring using PowerShell registry modification — a documented Akira and Black Basta staging step.
Command
powershell.exe -Command "Set-MpPreference -DisableRealtimeMonitoring $true" Cleanup
powershell.exe -Command "Set-MpPreference -DisableRealtimeMonitoring $false" Expected Telemetry
Sysmon Event ID 1: powershell.exe with DisableRealtimeMonitoring in command line. Windows Defender event log records protection disabled.
Expected Detection
Alert fires on DefenseImpairment indicator. Cross-correlate with other staging indicators on same host.