huntrule

Windows SharpLdapWhoami Execution via LDAP Whoami Methods

Flags execution of SharpLdapWhoami on Windows using LDAP-related whoami alternative method parameters.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-29
Updated
2026-07-31
AnalysisDetection

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. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags execution of SharpLdapWhoami on Windows when the process image or metadata indicates the tool. It further matches command lines using LDAP/NTLM/Kerberos negotiation methods such as /method:{ntlm,kerb,nego} and /m:{ntlm,kerb,nego}. This matters because the tool can be used to discover identity context by querying LDAP against a domain controller. Telemetry required includes Windows process creation data with image path, file name/product metadata, and full command-line arguments.

Reporting behind it

Related detections9 linkedT1033 — drag to rearrange
Suspicious Whoami Discovery Spawned by Windows Script Host via Process Creation (via process_creation)
Suspicious Localized Administrator Account and Group Enumeration After Citrix Bleed Exploitation
Malicious Recon Output Staged in Qlik Sense Fonts Directory by Cactus Ransomware
Suspicious Host Reconnaissance Command Chain via cmd
Malicious Child Process Spawned From n8n Node Process
Suspicious Credential Enumeration via cmdkey List
Suspicious IIS Worker Process Spawning Whoami Reconnaissance
Suspicious Whoami Execution With Output Redirected to a File (via process_creation)
Possible Logged-On Session Discovery via Quser or Qwinsta (via process_creation)
Windows SharpLdapWhoami Execution via LDAP Whoami Methods
Pivot detection · T1033 · 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.