Possible PowerShell Empire Default User-Agent In HTTP Traffic

ATT&CK techniques

C2

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
- T1071.001Web Protocols
Exfiltration
Impact

What it detects

This rule detects outbound HTTP traffic carrying the default user-agent string shipped with the PowerShell Empire C2 framework. In the WithSecure C2 and Exfiltration Lab 1 the Empire agent beacons out with an unmodified Mozilla compatible MSIE user-agent that is characteristic of the framework default profile. Attackers rely on this static header for their staging and command channel unless an operator customizes it.

Reporting behind it

Related detections9 linkedT1071.001 — drag to rearrange

Malicious Data Exfiltration via curl with Stealer Specific BuildID Header

Suspicious Shadow File Exfiltration Over Dev TCP on Linux via Process Creation (via process_creation)

Suspicious Netcat Reverse Shell via Named Pipe on Linux via Process Creation (via process_creation)

Malicious GenAI Browser Extension C2 and PAC Redirection (via proxy)

Possible Prometei Botnet C2 URI Pattern

Malicious PUBLOAD Fake Windows Update C2 Request via Proxy (via proxy)

Possible Lampion C2 Beacon With dados Parameter

Suspicious Non-Standard HTTP Methods Used for Covert C2 (via proxy)

Malicious Splinter Post-Exploitation Implant C2 URI Pattern (via proxy)

Possible PowerShell Empire Default User-Agent In HTTP Traffic

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.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →