Proxy Execution via MSBuild Running Inline Task XML

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-13
Updated
2026-09-13

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects msbuild.exe executing a standalone .xml project file, the NOOPLDR loading technique used in Cuckoo Spear to run inline C# tasks and evade application control. MSBuild consuming a loose XML file rather than a solution or project is a common trusted-developer-utility abuse pattern.

Related detections7 linkedT1127.001 — drag to rearrange
MSBuild Executing Non-Project File or Remote Payload
Antivirus Check and Remote Loader Retrieval in LNK Command Chain
Suspicious MSBuild Execution From Office or Archive Extraction Context (via process_creation)
Suspicious MSBuild Execution from Writable Directory (via process_creation)
In-Memory MSBuild Proxy Execution of a Project From a User-Writable Path (via process_creation)
Suspicious MSBuild LOLBin Spawning Script Interpreter (via process_creation)
Windows msbuild.exe Network Connections to Ports 80/443
Proxy Execution via MSBuild Running Inline Task XML
Pivot detection · T1127.001 · 7 related

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