Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-09-12
Updated
2026-09-12

ATT&CK techniques

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

What it detects

This rule detects outbound HTTP requests carrying the UAT-10608 command-and-control beacon layout where the URI encodes the victim host, the harvesting phase and a campaign identifier as h, l and id parameters. This structured query pattern is used by the credential harvesting operation to report progress and exfiltrate results over HTTP. Matching traffic indicates an actively beaconing compromised host.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious Phishing Data Exfiltration to SheetBest API by GitBait Campaign (via proxy)
Malicious NPM Backdoor C2 Beacon to Injective Telemetry Endpoint via Proxy
Suspicious CurKeep Backdoor C2 API Endpoints (via proxy)
Suspicious Error 524 Decoy Smishing Phishing Endpoint Access (via proxy)
Windows Process Execution of Common Tunneling Tools (httptunnel, plink, socat, stunnel)
Possible GammaSteel C2 Using Spoofed iPhone User Agent
Suspicious PolarEdge Backdoor C2 URL with Module and putdata Command (via proxy)
Suspicious Interlock Backdoor C2 Beacon to init1234 Endpoint (via proxy)
Possible FakeBat Loader Payload Download and C2 URI Patterns
Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP
Pivot detection · T1071.001 · 9 related

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