PowerShell DNSExfiltrator command usage (DNSExfiltration)

Detects PowerShell use of Invoke-DNSExfiltrator for DNS/DoH-based exfiltration based on Script Block Logging content.

FreeReviewedSigma · High · v2
Product
windows
Category
ps_script
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-01-07
Updated
2026-07-31

ATT&CK techniques

Exfiltration
  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. C2

  13. Impact

What it detects

This rule identifies PowerShell script block content that references the Invoke-DNSExfiltrator functionality with parameters indicating exfiltration over DNS, including options consistent with DoH usage. Attackers use DNS covert channels to move data while blending into common network traffic patterns and reducing visibility of direct outbound transfers. The detection relies on Script Block Logging telemetry and matches the presence of specific command text and required parameter fragments within the executed script block.

Related detections9 linkedT1048 — drag to rearrange
Suspicious Data Exfiltration via Blat SMTP Client (via process_creation)
Suspicious blat Utility Used for SMTP Data Exfiltration
Suspicious Data Exfiltration via WinSCP Command Line in BlackSuit Ransomware
Suspicious Scheduled Task Creation for rclone Exfiltration by The Gentlemen RaaS (via process_creation)
Suspicious DNS Query for Tor Onion Domain
Possible DNS Tunneling via Excessively Long Query Name
Malicious Bulk Data Exfiltration via Rclone (via process_creation)
BITS Payload Downloaded via Commandline (via process_creation)
BITS Payload Downloaded via PowerShell (via powershell)
PowerShell DNSExfiltrator command usage (DNSExfiltration)
Pivot detection · T1048 · 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.