Windows Process Creation: AdFind Executed with Suspicious Recon Flags

Detects AdFind executions on Windows that include common AD reconnaissance parameters.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Janantha Marasinghe (https://github.com/blueteam0ps), FPT.EagleEye Team, omkar72, oscd.community (SigmaHQ), DRL 1.1
Published
2021-02-02
Updated
2026-07-30

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags AdFind launched with command-line arguments commonly associated with Active Directory discovery and related reconnaissance. Such usage matters because attackers may query domain information (including domain admin-related targets and computer/domain enumeration flags) to map environments before further exploitation. It relies on Windows process creation telemetry and matching specific AdFind command-line substrings.

Related detections9 linkedT1069.002 — drag to rearrange
Windows Process Creation: Renamed AdFind.exe Executions
Suspicious Active Directory Enumeration via ADWS PowerShell Cmdlets via ps_script
Windows File Events: ADExplorer .dat Snapshot Written by ADExp.exe or ADExplorer.exe
Windows: Sysinternals ADExplorer invoked with snapshot flag to create AD database snapshot
Windows Process Creation: Sysinternals ADExplorer Snapshot Exports Active Directory Database
Windows PowerShell module commandlet names matching known exploitation and post-exploitation tooling
Windows Process Creation: Suspicious PowerShell Commandlets Used by Known Exploitation Tools
Windows file creation for SharpHound/BloodHound collection output filenames
Windows LDAP Client Event ID 30 Active Directory enumeration via LDAP search filters
Windows Process Creation: AdFind Executed with Suspicious Recon Flags
Pivot detection · T1069.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.