Windows Registry: lsass.exe Creating Local Hidden User Account Entries

Alerts when lsass.exe writes hidden local user name entries to the SAM\...\Users\Names\ registry path.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_event
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-05-03
Updated
2026-07-30

ATT&CK techniques

Persistence
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Sysmon registry events where lsass.exe writes to the SAM registry path for hidden local user names under \SAM\SAM\Domains\Account\Users\Names\, matching entries that end with '$\(Default)'. Attackers may use this technique to establish persistence by creating hidden local accounts that are harder to enumerate through standard user listings. Detection relies on registry event telemetry with the TargetObject value and the process path of lsass.exe.

Related detections9 linkedT1136.001 — drag to rearrange
Suspicious Rogue Administrator Account Creation Named System32 (via process_creation)
Suspicious Local Account Creation via Net User in Pre-Ransomware Phase
Suspicious Hidden Local Account Creation via Net User by UAT-8099
Malicious Local Account Creation of Support or Whiteninja via net.exe
Malicious Dynamicweb Unauthenticated Administrator Creation via Setup Default.aspx (via webserver)
Suspicious Hidden Backdoor Account Creation Ending With Dollar Sign (via process_creation)
Malicious User Creation via Commandline (via process_creation)
Suspicious Local Account Creation and Privileged Group Addition via Net.EXE (via process_creation)
Suspicious Hidden Local Account Creation via Dscl (via process_creation)
Windows Registry: lsass.exe Creating Local Hidden User Account Entries
Pivot detection · T1136.001 · 9 related

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