huntrule

Windows svchost.exe Spawned by Uncommon Parent Process

Alerts when svchost.exe starts with an unusual parent process name on Windows.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-08-15
Updated
2026-07-30
AnalysisDetection

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 process creation events where the child process is svchost.exe and the parent process is not among a set of common Windows service-related binaries. Attackers may use svchost as a living-off-the-land style proxy to blend in with normal Windows activity, so deviations in the parent lineage can be a useful stealth indicator. It relies on process creation telemetry that includes Image and ParentImage values, specifically matching svchost.exe by filename and excluding known benign parents.

Reporting behind it

Related detections9 linkedT1036.005 — drag to rearrange
Suspicious Loading of Masqueraded EndpointDlp.dll Backdoor
Suspicious svchost.exe Execution from Public Directory (via process_creation)
Suspicious Process Masquerading as apached via GobRAT Bulbature Implant
Suspicious MicrosoftEdgeUpdate Launched with Dat Config File
Malicious Scheduled Task Masquerading as Defender NisSrv via Schtasks
Malicious PowerShell Masquerading as Windows Terminal in ProgramData (via process_creation)
Suspicious Csrss Process Masquerading Outside System32 (via process_creation)
Suspicious Mimilite Credential Dumper Execution Writing KB-Named Output
Suspicious PikaBot Autorun Persistence Pointing to AppData Microsoft Dropzone via registry_set
Windows svchost.exe Spawned by Uncommon Parent Process
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.