Windows Process Creation: Detect Sysinternals Tool Name Impersonation by Executable

Alerts on Windows process executions using filenames that match common Sysinternals tools to indicate potential binary impersonation.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
frack113, Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-12-20
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 process executions on Windows where the image filename ends with the name of well-known Sysinternals utilities (including 64-bit and ARM64 variants). Attackers may impersonate legitimate Sysinternals binaries by naming malicious executables to blend in and evade allowlists or naive detections. It relies on process creation telemetry with the full image path/filename, filtering out events associated with Sysinternals publisher/product metadata.

Related detections9 linkedT1202 — drag to rearrange
Windows ConHost Spawning Suspicious Script and Command-Line Child Processes
Suspicious Child Process Creation from BgInfo.EXE on Windows
Windows: Suspicious Child Process Spawned by VsCode code.exe
Windows WSL Process Spawning Uncommon Child Executables
Windows: Alert on Unusual Child Process of Setres.EXE Spawning 'choice' Executables
Windows ZipExec-Style Suspicious PowerShell/Command Execution with Password-Protected ZIP
Windows: Cmdl32.EXE Arbitrary File Download Indicator via /vpn and /lan Flags
Windows Process Creation: WSL (wsl.exe) Used for Arbitrary Command Execution
Windows renamed dctask64.exe execution via known IMPHASH values
Windows Process Creation: Detect Sysinternals Tool Name Impersonation by Executable
Pivot detection · T1202 · 9 related

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