Windows Process Creation: Renamed msdt.exe Execution

Flags Windows process creation where OriginalFileName is msdt.exe and the executable appears to be a renamed copy.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
pH-T (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-03
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 identifies process executions where the binary reports OriginalFileName as msdt.exe, while the on-disk image path ends with \msdt.exe, indicating a renamed copy. Attackers may use trusted-looking system utilities under altered filenames to evade detection and maintain stealth. It relies on Windows process creation telemetry with access to the process image path and the file’s OriginalFileName metadata.

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)
Renamed Execution of a Renamed Windows System Utility (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
Windows Process Creation: Renamed msdt.exe Execution
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.