Malicious Bumblebee Loader User-Agent In Web Traffic

PremiumReviewedSigma · High · v1
Category
proxy
Author
HuntRule
Published
2026-10-05
Updated
2026-10-05

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 the hardcoded User-Agent string Bumblebee Loader in outbound web traffic, the beacon signature of the Bumblebee loader as it contacts its command-and-control server. Bumblebee stages Cobalt Strike and hands off access to ransomware affiliates. The self-identifying User-Agent uniquely marks infected hosts checking in.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious FvncBot Device Registration Request Over HTTP
Malicious 3CX Second-Stage C2 Icon Retrieval from GitHub IconStorages (via dns_query)
Suspicious PowerShell Web Request to oastify Out-of-Band Domain
Suspicious AstarionRAT HTTP Beacon Cookie Values
Suspicious osascript Spawning curl to High Port C2 via process_creation
Suspicious PowerShell Spawned by Web Browser
Suspicious Outbound Request to Webhook.site Interaction Service
Malicious C2 Communication via cur1-request User-Agent on macOS
Suspicious AdaptixC2 Beacon Status Request by JadeProx TriBack Loader (via proxy)
Malicious Bumblebee Loader User-Agent In Web Traffic
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.