Windows Suspicious Parent Processes: Unusual Child Creation by System Utilities

Alerts when predefined suspicious Windows parent executables spawn unusual or unrecognized child processes.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-03-21
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. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows process creation events where the parent process image ends with specific binaries (e.g., minesweeper.exe, winver.exe, bitsadmin.exe, csrss.exe, certutil.exe, eventvwr.exe, calc.exe, notepad.exe). These parent processes are expected to have limited, normal child behavior; attackers may use them to blend into user/system activity. It relies on process creation telemetry including parent and child image paths, plus exclusions for known benign child executables and null image values.

Related detections9 linkedT1036 — drag to rearrange
Suspicious GitHub Actions Runner In Hidden Directory via Shell (via process_creation)
Suspicious Billbug Loader Artifacts in Windows Temp Directory
Malicious Scheduled Task Masquerading as Windows Defender Sync via schtasks (via process_creation)
Malicious Startup Persistence via WindowsDefenderSync Shortcut (via file_event)
Malicious PXA Stealer Archive Extraction via Renamed WinRAR images.png (via process_creation)
Malicious NimDoor Loader Persistence via Masqueraded Google Updater (via file_event)
Suspicious Rename of Double-Extension PowerShell Script (via process_creation)
Suspicious Cobalt Strike OCSP Malleable C2 Profile Traffic
Suspicious Spoofed Microsoft Host Header C2 by Stately Taurus
Windows Suspicious Parent Processes: Unusual Child Creation by System Utilities
Pivot detection · T1036 · 9 related

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