PowerShell Script Creates Volume Shadow Copy via Win32_ShadowCopy

Alerts when PowerShell script blocks invoke Win32_ShadowCopy.Create to create a ClientAccessible shadow copy.

FreeReviewedSigma · High · v2
Product
windows
Category
ps_script
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-01-12
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags PowerShell script content that references the Win32_ShadowCopy WMI class and uses a Create call with the ClientAccessible option. Attackers may use Volume Shadow Copy to access or duplicate sensitive data, including credential-related files, from a point-in-time snapshot. Detection relies on Script Block Logging telemetry that captures the PowerShell script text for specific string patterns indicating the shadow copy creation.

Related detections9 linkedT1003.003 — drag to rearrange
Malicious NTDS.dit Extraction via Ntdsutil (via process_creation)
Malicious NTDS Extraction via ntdsutil IFM (via process_creation)
Malicious NTDS Database Staging to Audit Directory (via file_event)
IFM Creation Detected from Commandline - Installation from Media (via process_creation)
Malicious Credential Hive Copy from Volume Shadow Copy
Malicious File Copy via Esentutl Volume Shadow Access (via process_creation)
Malicious NTDS Extraction via NetExec (via process_creation)
Malicious Active Directory Database Dump via ntdsutil IFM (via process_creation)
Malicious NTDS Extraction via Ntdsutil IFM Media Creation
PowerShell Script Creates Volume Shadow Copy via Win32_ShadowCopy
Pivot detection · T1003.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.