huntrule

Windows msdt.exe execution using PCWDiagnostic.xml answer file

Alerts on msdt.exe launched with PCWDiagnostic.xml and an answer-file argument, excluding cases from pcwrun.exe.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-13
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process creation events where msdt.exe is launched with a command line referencing \WINDOWS\diagnostics\index\PCWDiagnostic.xml and includes an answer-file argument ( -af ). Attackers may use this execution pattern to mimic legitimate diagnostic tooling behavior while running arbitrary logic through the msdt utility. It relies on Windows process creation telemetry, including the spawned Image path, full CommandLine, and the parent process name to exclude the specific expected parent (pcwrun.exe).

Reporting behind it

Related detections9 linkedT1218 — drag to rearrange
Suspicious .NET LOLBin Execution via CasPol or RegAsm
Possible DarkGate DLL Sideloading via iTunesHelper Loading CoreFoundation
Suspicious extrac32 CAB Extraction Abuse
Malicious cdb.exe Masquerading as fontdrvhost in ProgramData (via process_creation)
Malicious certutil Decodehex Payload Reconstruction by DarkGate
Malicious MSIX Package Execution via App Installer ms-appinstaller Protocol (via process_creation)
Malicious ViPNet Backdoor Loader via lumpdiag.exe Path Substitution
Suspicious BitLockerToGo Execution from Unusual Parent
Suspicious Proxy Execution via pcalua
Windows msdt.exe execution using PCWDiagnostic.xml answer file
Pivot detection · T1218 · 9 related

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