Windows Execution of cloudflared for Cloudflare Try/Quick Tunnel Ad-hoc Tunneling

Flags execution of cloudflared on Windows with -url arguments consistent with Cloudflare Quick Tunnel setup.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Sajid Nawaz Khan (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 identifies Windows process executions of the cloudflared binaries (cloudflared.exe or architecture-specific variants) with command-line arguments indicating tunnel URL usage and anti-auto-update behavior. Attackers can abuse Cloudflare Quick/Try Tunnel to expose internal services over an ad-hoc public endpoint for command-and-control, pivoting, or remote access. The detection relies on Windows process creation telemetry, specifically the executable name/path and command-line content (including -url, optional tunnel, and -no-autoupdate), plus matching against known cloudflared image hashes.

Related detections9 linkedT1090.001 — drag to rearrange
Malicious SOCKS Proxy Tunnel via Earthworm Rssocks by UAT-8837
Malicious Volt Typhoon Port Proxy Configuration via Netsh (via process_creation)
Suspicious netsh Port Proxy Configuration for Covert Tunneling
Malicious Port Forwarding Tunnel via Netsh Portproxy (via process_creation)
Windows Process Execution of Renamed cloudflared.exe with Tunnel/Run Command Arguments
Windows execution of cloudflared.exe from a non-default directory
Windows Process Creation: Chisel Tunneling Tool (chisel.exe) Execution
Windows SharpChisel Command-Line Execution via SharpChisel.exe
Windows WFP Event 5156: RDP traffic via loopback when hosted by svchost termsvcs
Windows Execution of cloudflared for Cloudflare Try/Quick Tunnel Ad-hoc Tunneling
Pivot detection · T1090.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.