Windows userinit.exe Spawns Uncommon Child Processes

Alerts when userinit.exe starts an unexpected child process during logon, suggesting potential persistence via modified logon behavior.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Tom Ueltschi (@c_APT_ure), Tim Shelton (SigmaHQ), DRL 1.1
Published
2019-01-12
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 flags process creation events where the parent process image ends with \userinit.exe and the resulting child process is not a known/common expected shell. Attackers may abuse the userinit launch path to start custom shells or login/persistence workflows immediately after user logon. The detection relies on Windows process creation telemetry, specifically ParentImage and the child process Image and CommandLine fields, with exclusions for common benign cases like Explorer, PowerShell on Windows Core, and selected vendor utilities.

Related detections4 linkedT1037.001 — drag to rearrange
Malicious Logon Script Persistence via UserInitMprLogonScript
Suspicious COLDRIVER Logon Script Persistence via UserInitMprLogonScript (via process_creation)
Windows Command Line Logon Script Persistence via UserInitMprLogonScript
Windows Registry Persistence via UserInitMprLogonScript Value
Windows userinit.exe Spawns Uncommon Child Processes
Pivot detection · T1037.001 · 4 related

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