Suspicious Account Disable via net user active no (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-06-03
Updated
2026-08-28

ATT&CK techniques

Impact
  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

What it detects

This rule detects net.exe disabling a user account with the active no flag, an action the Lotus Wiper performs to remove account access and deny defenders control of affected hosts. Disabling accounts supports the wiper goal of locking users out during a destructive campaign. Detecting this command surfaces account access removal activity.

Related detections9 linkedT1531 — drag to rearrange
AWS IAM SAML Provider Deletion via CloudTrail
Linux userdel Execution: User Account Deletion via userdel
Linux groupdel Executed to Delete a User Group
Windows Security Logoff Events (Event ID 4634/4647)
Windows PowerShell Script: Remove Account From Domain Admin Group via Remove-ADGroupMember
Okta User Account Lockout Triggered by Max Sign-In Attempts
Google Cloud: Service Account Disabled or Deleted via IAM Audit Events
Azure Kubernetes Service Service Account Modified or Deleted Activity Log Events
AWS ElastiCache Cache Security Group Modified or Deleted via CloudTrail
Suspicious Account Disable via net user active no (via process_creation)
Pivot detection · T1531 · 9 related

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