Malicious D3f@ck Loader C2 via Java User-Agent Ready Beacon (via proxy)

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

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 D3F@ck loader command-and-control traffic identified by the hardcoded Java/1.8.0_101 user-agent combined with an event=ready status parameter in the request URI. This loader reports staged status values such as ready, downloaded and finished to its C2. The fixed Java user-agent from a non-Java host is a strong indicator of the loader beacon.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious FIN7 DiceLoader C2 via Placeholder User-Agent (via proxy)
Suspicious AddInProcess32 Outbound Connection after Process Hollowing
Suspicious microsoftedgeupdatecore Outbound Connection from Wrong Path
Suspicious RegAsm or AppLaunch Outbound Connection after Injection
Malicious FakeBat Distribution Domain Lookup (via dns_query)
Suspicious Modification of Windows Hosts File
Malicious Fenix Botnet C2 Communication via QuantumService Domain (via dns_query)
Suspicious BLOODALCHEMY Command and Control URI Pattern via Proxy
Malicious MIMICRAT C2 HTTP Request Pattern (via proxy)
Malicious D3f@ck Loader C2 via Java User-Agent Ready Beacon (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.