huntrule

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
AnalysisDetection

ATT&CK techniques

Persistence

  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

  14. 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.

Reporting behind it

Related detections9 linkedT1136.001 — drag to rearrange
Suspicious Local Administrator Account Creation via Net Command via Process Creation (via process_creation)
Suspicious Rogue Machine Account Creation via Powermad New-MachineAccount
Malicious Local Administrator Account Added via net localgroup (via process_creation)
Malicious Switch User to Rogue Root-Equivalent Account troot (via process_creation)
Malicious Rogue F5 BIG-IP Administrator Account Creation via tmsh (via process_creation)
Suspicious Hidden Local Account Creation SqlDbAdmin via Process Creation
PowerShell Local Account Creation With Self-Deleting Script
Suspicious Creation of ctxsvc Local Account via net Command
Suspicious Local Administrator Account Addition via net localgroup
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.