Suspicious Cloudflared Tunnel Execution with Token

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-15
Updated
2026-08-28

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 detects execution of the cloudflared client to run a named tunnel with an embedded token, establishing an outbound encrypted channel that bypasses perimeter controls. Akira ransomware operators used cloudflared tunnels for covert remote access into victim networks. Unsanctioned tunneling tools provide attackers persistent command and control that evades firewall inspection.

Related detections9 linkedT1572 — drag to rearrange
Suspicious DNS Query to Dynamic DNS and Tunneling Providers Abused by RATs
Suspicious SSH Reverse Tunnel Over DNS Port
Suspicious Reverse SSH Tunnel Exposing Local SSH via process_creation
Suspicious OpenSSH Reverse Tunnel Creation via Process Creation
Suspicious OpenSSH Reverse Tunnel Establishment via process_creation
Suspicious LocalToNet Tunneling Tool Execution
Malicious RDP Tunneling via ngrok (via process_creation)
Suspicious UUID Named Pipe Created Consistent with Mythic SMB Agent
Malicious Chisel Reverse Tunnel Execution for Protocol Tunneling
Suspicious Cloudflared Tunnel Execution with Token
Pivot detection · T1572 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.