Renamed Execution of a Renamed Windows System Utility (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-06-18
Updated
2026-08-28

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 detects a built-in Windows system utility running under a filename that does not match its embedded original binary name, exposing a mismatch between the PE OriginalFileName and the on-disk image. Renaming trusted utilities such as cmd, powershell, certutil or rundll32 is a defense-evasion technique highlighted in the Red Canary Threat Detection Report that lets adversaries slip past name-based detections and application controls. Alerting on the OriginalFileName-to-image mismatch surfaces the evasion regardless of the alias chosen.

Related detections9 linkedT1036.003 — drag to rearrange
Renamed Autohotkey Binary
Suspicious Masqueraded Rundll32 with Mismatched Original Filename (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Suspicious Renamed Pythonw Interpreter Execution via XWorm Loader (via process_creation)
Suspicious PowerShell Masquerading as Windows Terminal via process_creation
Windows Schtasks Execution with Renamed schtasks.exe Binary
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Suspicious LOLBIN Copy From Windows System Directories Using Windows Copy Tools
Renamed Execution of a Renamed Windows System Utility (via process_creation)
Pivot detection · T1036.003 · 9 related

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