Possible ZharkBot C2 Beacon via socket Endpoint with Bot Parameters via proxy

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

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 ZharkBot command and control beacons that request a /socket/ endpoint with the structured query parameters id, bld, os, mn and us reporting bot, build and host details. This fixed parameter layout encodes victim registration data to the panel. Matching the endpoint and its parameter set fingerprints the bot check-in regardless of the C2 domain in use.

Related detections9 linkedT1071.001 — drag to rearrange
Possible Spectre Ops C2 Beacon via nico and yfat Query Parameters via proxy
Malicious Dropbox Cloud C2 via Spoofed Googlebot User Agent
Possible FluBot C2 Polling via Known Malware URI Paths
Malicious MetaStealer C2 via cpp-httplib User-Agent (via proxy)
Possible Cobalt Strike Beacon URI Pattern via Web C2
Malicious SharkBot Android Banking Trojan C2 via DGA Domain Suffix
Possible Team9 C2 via Emercoin bazar Domain Resolution
Suspicious Diamond Sleet Anomalous Microsoft Internet Explorer User Agent (via proxy)
Suspicious Diamond Sleet C2 via LambLoad Addon PHP URI Pattern (via proxy)
Possible ZharkBot C2 Beacon via socket Endpoint with Bot Parameters via proxy
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.