Windows PowerShell: Silence EmpireDNSAgent script matches DNS tunnel and remote shutdown/restart activity

Flags PowerShell ScriptBlockText that combines Empire process-control indicators with dnscat DNS tunneling commands.

FreeReviewedSigma · Critical · v2
Product
windows
Category
ps_script
Author
Alina Stepchenkova, Group-IB, oscd.community (SigmaHQ), DRL 1.1
Published
2019-11-01
Updated
2026-07-31

ATT&CK techniques

Execution → Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. Exfiltration

What it detects

This rule flags PowerShell script block logging where the script contains both Empire-like process control indicators (e.g., Stop-Computer/Restart-Computer and exception handling) and DNS tunneling behavior associated with Dnscat2 (including nslookup command execution and specific tunnel/session fields). The combined pattern matters because it can indicate coordinated remote command/control and host impact using a DNS-based channel. It relies on Windows PowerShell Script Block Logging telemetry to capture ScriptBlockText content for matching.

Related detections9 linkedT1059.001 — drag to rearrange
Malicious GS-Netcat Command and Control via Global Socket Relay Network (via dns_query)
Suspicious DNS Query to Dynamic DNS and Tunneling Providers Abused by RATs
Suspicious Script Download via Curl and PowerShell by Dohdoor
Malicious dnscat2 DNS Tunneling C2 Traffic
Malicious Metasploit Stager Delivery via mshta Remote HTA (via process_creation)
Suspicious Cloudflared Tunnel Persistence Installed via msiexec (via process_creation)
Suspicious PowerShell Download of Disguised Payload to ProgramData
Suspicious PowerShell WebClient Download of Executable Payload
Malicious Script Host Spawning PowerShell in Gootloader Chain
Windows PowerShell: Silence EmpireDNSAgent script matches DNS tunnel and remote shutdown/restart activity
Pivot detection · T1059.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.