Windows Process Creation: Visual Studio Code Tunnel (.exe tunnel) Execution

Flags cmd.exe-launched Visual Studio Code tunnel processes with expected tunnel and license-accept arguments on Windows.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems), citron_ninja (SigmaHQ), DRL 1.1
Published
2023-10-25
Updated
2026-07-30

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 process executions where a command line ends with ".exe tunnel" and includes required tunnel license acceptance arguments. It further correlates the parent context to cmd.exe executing code-server.cmd from the Stable servers directory, which is a strong indicator of VS Code tunnel startup. Attackers may abuse this feature to establish an outbound command-and-control path, making this behavior valuable for detecting suspicious tunnel launches. Telemetry relies on Windows process creation fields including Image, ParentCommandLine, and CommandLine.

Related detections9 linkedT1071.001 — drag to rearrange
Windows Process Creation: Visual Studio Code Tunnel Execution with Renamed Binary
Malicious HarborWatch RAT Command and Control Beacon by User Agent (via proxy)
Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP
Malicious BadIIS C2 Communication via lwxatisme User-Agent
Possible PS1Bot C2 Beacon With Drive Serial URI Pattern (via proxy)
Suspicious WarmCookie C2 Beacon With Fixed Firefox User-Agent
Suspicious n8n Campaign RMM Installer Masquerading as OneDrive Document
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
Malicious Renamed Python Interpreter Executing nvidia.py RAT
Windows Process Creation: Visual Studio Code Tunnel (.exe tunnel) Execution
Pivot detection · T1071.001 · 9 related

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