Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters

Detects execution of GoldenDMSA.exe with command-line indicators consistent with wordlist/bruteforce directory account manipulation.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2026-10-19
Updated
2026-10-21

ATT&CK techniques

Persistence → Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags process executions where the image path ends with GoldenDMSA.exe and the command line contains specific wordlist/bruteforce-related arguments. The behavior matters because attackers can use GoldenDMSA tooling to target Windows directory service account operations, including password/credential-related abuse patterns. It relies on Windows process creation telemetry, including the executable filename and command-line arguments.

Related detections9 linkedT1098 — drag to rearrange
Windows Security: Kerberos 4771 Pre-Authentication Failures for Machine Account Password Guessing
Suspicious Compute Instance Metadata Modification in GCP
Suspicious Azure AD Authentication Method Registration for Account Takeover (via azure)
Suspicious EC2 Instance Connect SSH Public Key Push (via cloudtrail)
Possible Kerberoasting via RC4 Service Ticket Requests
Suspicious Okta Application Self-Assignment to All Applications by UNC3944 (via cloud)
Malicious Active Directory ACL Manipulation via PowerView
Suspicious dMSA Membership Modification via msDS-GroupMSAMembership Attribute
Suspicious LDAP Query Enumerating Kerberos Preauth Disabled Accounts with Whitespace Evasion
Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters
Pivot detection · T1098 · 9 related

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