Windows: User Added to Highly Privileged Local/Directory Groups via net.exe or Add-LocalGroupMember

Flags net.exe or PowerShell commands adding users to privileged groups like Group Policy Creator Owners or Schema Admins.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2024-02-23
Updated
2026-07-30

ATT&CK techniques

Persistence → Priv Esc
  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 identifies process execution where a user is added to highly privileged groups, specifically “Group Policy Creator Owners” or “Schema Admins,” using either net.exe with localgroup /add or PowerShell’s Add-LocalGroupMember. Adding users to these groups can enable privilege escalation and persistence by granting elevated permissions. It relies on Windows process creation telemetry with command-line arguments to match the relevant add-to-group patterns.

Related detections9 linkedT1098 — drag to rearrange
Malicious Cluster-Admin Role Binding Creation (via audit)
Malicious User Password Change Using Current Hash Password - ChangeNTLM - Mimikatz (via security)
Suspicious Account Password Set to Never Expire. (via security)
Malicious Modification of a Computer Account SPN (via security)
Suspicious Massive Group Membership Changes (via security)
Malicious High Risk Active Directory Group Membership Change (via security)
Malicious Account Marked as Sensitive and Cannot Be Delegated Had Its Protection Removed (via security)
Malicious Host Constrained Delegation Settings Changed for Potential Abuse (Rubeus) - Kerberos Only (via security)
Malicious Host Set with Unconstrained Delegation (via security)
Windows: User Added to Highly Privileged Local/Directory Groups via net.exe or Add-LocalGroupMember
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.