Windows Process Masquerading as svchost.exe via Binary Name and Location

Alerts on svchost.exe-named processes launched from non-standard paths with OriginalFileName svchost.exe.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (SigmaHQ), DRL 1.1
Published
2024-08-07
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 the executable filename ends with \svchost.exe but the process is not the legitimate svchost.exe from C:\Windows\System32 or C:\Windows\SysWOW64. It also requires that the process has the OriginalFileName set to svchost.exe, indicating intent to masquerade as the legitimate system binary. Masquerading like this is commonly used to evade defenses that rely on process names, so the rule relies on process creation telemetry including Image path and OriginalFileName.

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 Process Masquerading as svchost.exe via Binary Name and Location
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.