Windows File Events: NTDS.DIT Created by Suspicious or Rare Process

Alerts on creation of ntds.dit on Windows when the creator process image/path is uncommon or located in suspicious directories.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Florian Roth (Nextron Systems), Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-01-11
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. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags creation of a file ending with \ntds.dit, the Active Directory database, when the creating process is uncommon or originates from commonly abused directories. Attackers may target NTDS.DIT to obtain credential material by forcing it to be written or manipulated outside normal system workflows. The detection relies on Windows file event telemetry that includes the target filename and the process image path for the write/creation event.

Related detections9 linkedT1003.002 — drag to rearrange
Malicious Credential Hive Copy from Volume Shadow Copy
Windows Print.EXE Sensitive File Dump for Credential Access
Zeek SMB: Network Share File Transfers of Credential-Related Filenames
Zeek SMB Files: Impacket SecretDump Access to ADMIN$ and System32 .tmp Droppers
Windows Credential Dump Tool Artifacts Written to Disk via File Events
Windows Volume Shadow Copy Symlink Creation Using mklink
Windows Network Share File Transfers Targeting Credential and Memory Dump Paths
Windows Shadow Copy Creation via PowerShell/pwsh/wmic/vssadmin Commands
Windows: Detect esentutl.exe Copying Sensitive Credential Files via VSS
Windows File Events: NTDS.DIT Created by Suspicious or Rare Process
Pivot detection · T1003.002 · 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.