Windows Process Creation: Alert on Suspicious Parent of Core System Executables

Flags when core Windows executables (e.g., svchost, lsass, winlogon) are spawned by suspicious parent processes.

FreeReviewedSigma · Low · v1
Product
windows
Category
process_creation
Author
vburov (SigmaHQ), DRL 1.1
Published
2019-02-23
Updated
2026-07-30

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process creation events where a well-known system executable is launched with an uncommon or suspicious parent process. Attackers may use living-off-the-land techniques or process masquerading to blend into normal Windows activity, making parent-child process relationships important for triage. It relies on process creation telemetry including the child Image path and the ParentImage path, with additional exclusions for known benign parent locations and Defender-related parents.

Related detections9 linkedT1036.005 — drag to rearrange
Suspicious ALPHA SPIDER Rclone Exfiltration Tool Masquerading as System Binary (via process_creation)
Suspicious Axios NPM macOS Persistence Masquerading as Apple Service
Malicious Spoolsv Process Masquerading From Non-System Path (via process_creation)
Suspicious svchost.exe Execution From AppData Roaming Directory
Malicious StyleSmuggler (CVE-2026-75650) Post-Exploitation Implant Process (via process_creation)
Malicious WezRat Persistence via Chrome Updater Run Key
Malicious ValleyRAT RuntimeBroker Masquerade in RunTime Directory
Suspicious Execution of spools.exe from Public Directory
Malicious Fake Fortinet Patch Infostealer Execution (via process_creation)
Windows Process Creation: Alert on Suspicious Parent of Core System Executables
Pivot detection · T1036.005 · 9 related

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