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
Chisel Reverse Tunnel Tool Execution from Temporary Directory
Malicious Anubis Ransomware Cloudflare Tunnel via cloudflared (via process_creation)
Obfuscated RDP Tunneling Configuration Enabled for Port Forwarding (via process_creation)
Malicious RDP Tunneling (via rdp)
Suspicious SSH Reverse Tunnel via Renamed plink Utility on Triofox Host
Suspicious OpenSSH Reverse Tunnel Establishment via ssh.exe
Suspicious HelloNet SSH Reverse Tunnel via frontpage.exe (via process_creation)
Possible Ngrok RDP Tunnel Exposure via TCP 3389
Malicious Cloudflared Tunnel Established with Token
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.