Empire C2 Proxy Requests with Specific User-Agent and POSTed PHP URIs

Flags proxy HTTP POSTs using an Empire-like user agent to specific admin/login PHP endpoints.

FreeReviewedSigma · High · v2
Category
proxy
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2020-07-13
Updated
2026-07-31

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 flags proxy traffic where a specific Empire-like Windows user agent is combined with POST requests to a defined set of PHP endpoints (/admin/get.php, /news.php, /login/process.php). Attackers using Empire can blend command-and-control traffic into normal web requests by using recognizable URI patterns and consistent client fingerprints. Detection relies on proxy logs that capture HTTP method, the full request URI path, and the user-agent header.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious HTTP User Agent zzhbot From Docker API Compromise
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
Empire C2 Proxy Requests with Specific User-Agent and POSTed PHP URIs
Pivot detection · T1071.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.