huntrule

Windows Registry: Detect esentutl.exe activity under VSS service keys

Flags registry changes under VSS service keys when initiated by esentutl.exe, consistent with VSS-related abuse.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_event
Author
Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research) (SigmaHQ), DRL 1.1
Published
2020-10-20
Updated
2026-07-30
AnalysisDetection

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 identifies Windows registry activity involving the Volume Shadow Copy Service (VSS) service subtree when the initiating process is esentutl.exe. Attackers may use VSS-related functionality to support credential access and other post-compromise objectives, making service initialization and processing relevant. It relies on registry event telemetry that records the TargetObject being modified and the Image path for the process (filtered to exclude Start-related entries).

Reporting behind it

Related detections9 linkedT1003.002 — drag to rearrange
Suspicious Registry Hive Dump via reg save to Disguised evt Files
Malicious NTDS Extraction from Volume Shadow Copy by RA World
Malicious Flax Typhoon SAM and SECURITY Registry Hive Dump via reg save (via process_creation)
Malicious Registry Hive Dump for Credential Access via reg save (via process_creation)
Suspicious Registry Hive Export of SAM and SECURITY for Credential Theft after FortiClient EMS Exploitation
Malicious Registry Hive Dump via reg save
Malicious SAM and SYSTEM Registry Hive Credential Dump via reg.exe (via process_creation)
Malicious Registry Hive Theft from Shadow Copy via Print LOLBIN
Malicious Volume Shadow Copy Access via Mklink to GLOBALROOT
Windows Registry: Detect esentutl.exe activity under VSS service keys
Pivot detection · T1003.002 · 9 related

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