Possible PowerShell Empire Default C2 URI Beaconing

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-11-03
Updated
2026-11-03

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 HTTP requests to the default request URIs used by the PowerShell Empire C2 framework. In the WithSecure C2 and Exfiltration Lab 1 an Empire agent beacons to server paths such as /admin/get.php and /login/process.php while impersonating a Microsoft-IIS server. Attackers use these hardcoded default routes for command retrieval and result submission over HTTP.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious APT29 Zulip C2 Communication via curl User-Agent (via proxy)
Suspicious DNS Query for TryCloudflare Tunnel Abused for Malware Delivery (via dns_query)
Malicious GhostLocker Ransomware C2 Communication via HTTP (via proxy)
Malicious Agent Tesla Loader Malformed User-Agent in HTTP Traffic (via proxy)
Malicious Interlock RAT FileFix Download-Cradle via PowerShell WebClient with PowerShell User-Agent (via ps_script)
Suspicious Cobalt Strike Malleable Profile Beaconing via Legacy MSIE9 User-Agent and IE Compatibility URIs (via proxy)
Malicious Cobalt Strike Default Named Pipe Activity
Malicious VoidLink Kernel Rootkit C2 Endpoints via HTTP (via proxy)
Malicious EtherRAT C2 Exfiltration Endpoints via HTTP (via proxy)
Possible PowerShell Empire Default C2 URI Beaconing
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.