Windows DNS Queries for Cloudflared Tunnel Domains

Alerts on Windows DNS queries for domains ending with common Cloudflared tunnel hostnames.

FreeReviewedSigma · Medium · v2
Product
windows
Category
dns_query
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-12-20
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 DNS requests on Windows where the queried name ends with Cloudflared tunnel-related domains. Attackers may abuse these tunnels to support command-and-control activity, including establishing connectivity for remote access or persistence. It relies on DNS query telemetry containing the QueryName field to match the specified domain suffixes.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious UUID Named Pipe Created Consistent with Mythic SMB Agent
Windows DNS Queries to Devtunnels .devtunnels.ms Domains
Windows Process Execution of Common Tunneling Tools (httptunnel, plink, socat, stunnel)
Malicious Agent Tesla Loader Malformed User-Agent in HTTP Traffic (via proxy)
Malicious Interlock RAT FileFix Download-Cradle via PowerShell WebClient with PowerShell User-Agent (via ps_script)
Suspicious Cobalt Strike Malleable Profile Beaconing via Legacy MSIE9 User-Agent and IE Compatibility URIs (via proxy)
Suspicious SSH Reverse Tunnel Establishment (via process_creation)
Suspicious Cloudflared Tunnel Persistence Installed via msiexec (via process_creation)
Malicious Cobalt Strike Default Named Pipe Activity
Windows DNS Queries for Cloudflared Tunnel Domains
Pivot detection · T1071.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.