Malicious HTTP User Agent zzhbot From Docker API Compromise

PremiumReviewedSigma · High · v1
Category
proxy
Author
HuntRule
Published
2026-09-15
Updated
2026-09-15

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 outbound HTTP requests using the User-Agent string zzhbot which the vurl reverse connection tool sets when beaconing to its command and control infrastructure in the campaign targeting exposed Docker APIs.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious Cobalt Strike Default Named Pipe Activity
Malicious VoidLink Kernel Rootkit C2 Endpoints via HTTP (via proxy)
Malicious EtherRAT C2 Exfiltration Endpoints via HTTP (via proxy)
Possible PlugX and NPS Proxy Command and Control Domain Lookup
Possible Backdoor Mistic Command and Control Domain Lookup
Suspicious Weaver Ant In-Memory Web Shell Marker in Web Request (via webserver)
Malicious BlueNoroff C2 Communication via cur1-agent User-Agent (via proxy)
Possible GammaSteel C2 Using Spoofed iPhone User Agent
Suspicious PolarEdge Backdoor C2 URL with Module and putdata Command (via proxy)
Malicious HTTP User Agent zzhbot From Docker API Compromise
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.