Suspicious dMSA Object Access with Migration AccessMask

PremiumReviewedSigma · Medium · v1
Product
windows
Service
security
Author
HuntRule
Published
2026-10-22
Updated
2026-10-22

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects access to a delegated Managed Service Account object with the AccessMask 0x20 that corresponds to the dMSA migration operation. The BadSuccessor technique reads and manipulates dMSA objects to hijack privileges of a preceding account. This object access pattern helps surface abuse of the dMSA migration workflow.

Related detections9 linkedT1098 — drag to rearrange
Windows Security: Local Administrators Group Membership Change (Event 4732)
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters
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)
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious Okta Application Self-Assignment to All Applications by UNC3944 (via cloud)
Suspicious dMSA Object Access with Migration AccessMask
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.