Windows Executable Connections to Dead Drop Resolver Domains Excluding Common Browsers

Flags non-browser Windows executables making outbound connections to known dead-drop resolver domain patterns.

FreeReviewedSigma · High · v2
Product
windows
Category
network_connection
Author
Sorina Ionescu, X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-17
Updated
2026-07-31

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 flags when a non-browser executable initiates network connections to a set of commonly used, legitimate web domains and subdomains that have been observed serving as dead drop resolvers. Such traffic can help attackers blend command-and-control or staging activity into normal web access patterns. It relies on Windows network connection events with destination hostname matching against the configured domain list and process image-based exclusions for common browsers and select legitimate clients.

Related detections9 linkedT1102 — drag to rearrange
Windows Network Connections to azurewebsites.net from Non-Browser Processes
Possible Telegram API Command and Control DNS Query
Malicious Anubis Ransomware Cloudflare Tunnel via cloudflared (via process_creation)
Possible DNS Queries to Public Ethereum RPC Endpoints for EtherHiding Payload Retrieval (via dns_query)
Possible ITG05 Headlace Staging via Mocky and Mockbin Services (via proxy)
PowerShell Remote Download From Bunny CDN Host
Suspicious DNS Query for TryCloudflare Tunnel Abused for Malware Delivery (via dns_query)
Possible Access-Code Validation Beacon to Malware Delivery C2 (via proxy)
Suspicious Payload Retrieval from Cloudflare Tunnel via LOLBin (via process_creation)
Windows Executable Connections to Dead Drop Resolver Domains Excluding Common Browsers
Pivot detection · T1102 · 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.