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 Encrypted Reverse Shell via Netcat and GPG on Linux
Malicious axios NPM Supply Chain C2 Domain Resolution
Suspicious Reverse Shell via Dev TCP or Netcat
Malicious HarborWatch RAT Command and Control Beacon by User Agent (via proxy)
Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP
Malicious BadIIS C2 Communication via lwxatisme User-Agent
Possible PS1Bot C2 Beacon With Drive Serial URI Pattern (via proxy)
Suspicious WarmCookie C2 Beacon With Fixed Firefox User-Agent
Malicious Renamed Python Interpreter Executing nvidia.py RAT
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.