Windows Process Creation: Detect NTDS.DIT and Registry Hive Exfiltration Tooling

Detects suspicious Windows processes that reference NTDS.DIT/SYSTEM hive dumping or staging via common NTDS tooling and scripts.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-03-11
Updated
2026-07-30

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 Windows process executions whose command lines reference NTDS.DIT and related SYSTEM hive access patterns commonly used to stage credential database exfiltration. It matches known dumping binaries by filename (NTDSDump/NTDSDumpEx) as well as PowerShell scripts containing NTDSgrab.ps1 and other NTDS/IFM-style one-liners (ntdsutil, copy commands, and related create full output). It relies on process creation telemetry including Image, CommandLine, and ParentImage, enabling detection of suspicious collection and staging activity based on how NTDS.DIT is referenced and where related artifacts are written.

Related detections9 linkedT1003.003 — drag to rearrange
Suspicious Active Directory Snapshot Creation via ntdsutil
Malicious NTDS Credential Dump via Ntdsutil IFM Snapshot (via process_creation)
Malicious NTDS Database Dump via ntdsutil
Malicious NTDS Extraction from Volume Shadow Copy by RA World
Malicious NTDS Extraction via ntdsutil IFM
Malicious NTDS.dit Access via Shadow Copy GLOBALROOT Path
Suspicious Shadow Copy Creation via WMIC (via process_creation)
Malicious NTDS Extraction via Ntdsutil IFM
Malicious NTDS.dit Credential Extraction via ntdsutil
Windows Process Creation: Detect NTDS.DIT and Registry Hive Exfiltration Tooling
Pivot detection · T1003.003 · 9 related

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