TAG-144 Payload Staging via MyCustomAgent User-Agent (via proxy)

PremiumReviewedSigma · High · v1
Category
proxy
Author
HuntRule
Published
2026-06-07
Updated
2026-08-28

ATT&CK techniques

C2
  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. Exfiltration

  13. Impact

What it detects

This rule detects HTTP requests using the hardcoded MyCustomAgent/1.0 user-agent that the TAG-144 loader sets when pulling staged payloads from paste services via ServerXMLHTTP. Adversaries leverage a fixed non-browser user-agent to fetch second-stage code, making this distinctive string a reliable delivery-stage indicator.

Related detections9 linkedT1105 — drag to rearrange
Malicious Curl Download From C2 CAPTCHA Path via Process Creation
Malicious C2 Download Embedding Host Reconnaissance in URL
Suspicious File Upload via curl Multipart Form
Possible GCleaner Loader C2 Check-in via cpa ping php Endpoint via proxy
Possible NetHealth Implant C2 Beacon URI Pattern
LightSpy macOS Implant PID File Creation in Users Shared
Possible Remcos C2 Connection from eilowutil Process
Suspicious Remote HTA Payload Execution via MSHTA
Possible PurpleFox MSHTA to Msiexec Remote MSI Chain
TAG-144 Payload Staging via MyCustomAgent User-Agent (via proxy)
Pivot detection · T1105 · 9 related

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