Windows Network Connections to *.devtunnels.ms

Alerts on initiated Windows network connections to .devtunnels.ms hostnames, which may indicate remote access use.

FreeReviewedSigma · Medium · v2
Product
windows
Category
network_connection
Author
Kamran Saifullah (SigmaHQ), DRL 1.1
Published
2023-11-20
Updated
2026-07-31

ATT&CK techniques

C2 → Exfiltration
  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. Impact

What it detects

This rule flags network connections initiated by a process where the destination hostname ends with .devtunnels.ms. Such connections can be abused by attackers to establish command-and-control style access, including reverse shells or persistence mechanisms via the DevTunnels infrastructure. It relies on Windows network connection telemetry with fields indicating whether the connection was initiated and the destination hostname.

Related detections9 linkedT1572 — drag to rearrange
Suspicious SSH Reverse Tunnel Establishment (via process_creation)
Suspicious Cloudflared Tunnel Persistence Installed via msiexec (via process_creation)
Suspicious Renamed Tunneling Tool Executing from Windows Tasks Directory
Suspicious Reverse SSH Tunnel Creation with Host Key Verification Disabled (via process_creation)
Malicious Abyss Locker wmihelper SSH Backdoor Deployment (via file_event)
Malicious GS-Netcat Command and Control via Global Socket Relay Network (via dns_query)
Suspicious Microsoft Dev Tunnel Domain Resolution via DNS (via dns_query)
Suspicious DNS Query to Dynamic DNS and Tunneling Providers Abused by RATs
Suspicious SSH Reverse Tunnel Over DNS Port
Windows Network Connections to *.devtunnels.ms
Pivot detection · T1572 · 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.