Windows Execution of dnscat2 and iodine DNS Exfiltration/Tunneling Tools

Flags Windows execution of DNS tunneling/exfiltration tools identified by iodine.exe or dnscat2 in process creation events.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Daniil Yugoslavskiy, oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-24
Updated
2026-07-31

ATT&CK techniques

C2 → 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. Impact

What it detects

This rule identifies process executions on Windows where the binary path ends with iodine.exe or contains dnscat2. These tools are commonly associated with DNS-based exfiltration or tunneling, which can help attackers bypass conventional network controls. The detection relies on process creation telemetry, matching on the executed image filename/path.

Related detections9 linkedT1071.004 — drag to rearrange
Malicious Project CAV3RN DNS Configuration Recovery via cloudlanecdn.com (via dns_query)
Suspicious Long Alphanumeric DNS Subdomain Indicative of DNS Tunneling
Suspicious DNS Tunneling With Hex Subdomain To info Domain (via dns_query)
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 UPSTYLE Command Channel Pattern in Web Requests via CVE-2024-3400
Suspicious DNS C2 to Microsoft Typosquat Domain
Suspicious DNS Queries to Simitor Tracking Tunnel Infrastructure
Suspicious DNS Queries to Secshow Open Resolver Scanning Infrastructure
Windows Execution of dnscat2 and iodine DNS Exfiltration/Tunneling Tools
Pivot detection · T1071.004 · 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.