Windows: Suspicious CustomShellHost.exe execution spawned by non-Explorer parent

Alerts on CustomShellHost.exe executions where explorer.exe is not the expected parent process image.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-19
Updated
2026-07-31

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 process creation events where the parent process image ends with \CustomShellHost.exe, but the corresponding child process is not located under C:\Windows\explorer.exe. CustomShellHost is a signed Windows binary that attackers may misuse to reduce visibility and evade defenses. The detection relies on Windows process creation telemetry, specifically the parent image path ending pattern and the child image path matching explorer.exe.

Related detections9 linkedT1216 — drag to rearrange
Suspicious PowerShell Execution via SyncAppvPublishingServer LOLBIN
PowerShell Proxy Execution via SyncAppvPublishingServer (via process_creation)
Malicious Command Injection via SyncAppvPublishingServer VBS LOLBin (via process_creation)
Suspicious winrm.vbs LOLBAS Script Execution for Code Proxying
Windows: Code execution via Pester.bat invoked by PowerShell (Invoke-Pester/Get-Help)
Windows: Uncommon Child Processes Spawned by sigverif.exe
PowerShell: Signed UtilityFunctions.ps1 Loading Managed DLL via Proxy Execution
Windows PowerShell Script Proxy Execution via CL_mutexverifiers.ps1
PowerShell Assembly Loading via CL_LoadAssembly.ps1 Functions
Windows: Suspicious CustomShellHost.exe execution spawned by non-Explorer parent
Pivot detection · T1216 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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