Suspicious HTTP Beacon with Java Agent User-Agent (via proxy)

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

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 carrying the anomalous Java/Agent User-Agent string associated with the Group-IB XMRig covert Linux PAM abuse campaign command and control channel. The value mimics a legitimate Java runtime User-Agent but is malformed and specific to the tooling. Flagging this string helps surface miner command and control or payload retrieval traffic on the network.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious AdaptixC2 Beacon Status Request by JadeProx TriBack Loader (via proxy)
Possible GoldFactory GoldPickaxe Mobile Trojan C2 API Calls
Malicious Phishing Data Exfiltration to SheetBest API by GitBait Campaign (via proxy)
Suspicious Telegram Bot API getUpdates Polling for C2 by Millenium RAT (via proxy)
Possible Telegram Bot API Command and Control Traffic
Possible Lazarus C2 Beacon to Uncommon Port 1224 Loader Endpoints
Possible Cobalt Strike Beacon via Default Malleable Profile URIs
Possible Godfather Android Banking Trojan C2 Endpoints
Possible EndRAT C2 Communication via Distinctive Client Identifier
Suspicious HTTP Beacon with Java Agent User-Agent (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.