Windows msdt.exe Creating Files in Common Startup and Public Directories

Alerts when msdt.exe writes files to high-suspicion directories that may indicate persistence after exploitation.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Vadim Varganov, Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-24
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags file creation events where msdt.exe (msdt.exe) writes to directories commonly used for persistence or where attackers may stage payloads, including the Desktop, Startup folders, C:\PerfLogs, C:\ProgramData, and C:\Users\Public. Such activity can indicate exploitation that leverages msdt.exe to place files for follow-on execution. It relies on Windows file event telemetry capturing both the process image path and the target filename of created files.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Autorun Registry Persistence via sausageLoop Run Key
Malicious BabyLockerKZ Run Key Persistence
Suspicious Run Key Persistence Pointing To User-Writable Path
Malicious Ctrlpanel Run Key Autostart Persistence (via registry_set)
Persistence Run Key Pointing to svchost.exe in AppData Roaming
URL Shortcut File Created in Startup Folder for Persistence
Suspicious Run Key Persistence via UpdateCheck Value in Operation TrueChaos
Suspicious Run Key Persistence Pointing to AppData Local Copy
Malicious WezRat Persistence via Chrome Updater Run Key
Windows msdt.exe Creating Files in Common Startup and Public Directories
Pivot detection · T1547.001 · 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.