Windows svchost RDP via Reverse SSH Loopback Tunnel to 127.0.0.0/8:3389

Flags svchost.exe opening RDP (TCP 3389) connections to loopback, consistent with tunneled reverse access behavior.

FreeReviewedSigma · High · v2
Product
windows
Category
network_connection
Author
Samir Bousseaden (SigmaHQ), DRL 1.1
Published
2019-02-16
Updated
2026-07-31

ATT&CK techniques

Lateral Movement → 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. Collection

  11. Exfiltration

  12. Impact

What it detects

This rule identifies Windows network connections where svchost.exe initiates traffic from TCP port 3389 to a loopback destination (127.0.0.0/8 and ::1). Loopback-only RDP traffic can indicate that an attacker is relaying RDP through a local tunnel to evade direct remote exposure and complicate monitoring. Detection relies on network connection telemetry including process image path, connection initiation state, source port, and destination IP.

Related detections9 linkedT1572 — drag to rearrange
Obfuscated RDP Tunneling Configuration Enabled for Port Forwarding (via process_creation)
Malicious RDP Tunneling (via rdp)
Possible Ngrok RDP Tunnel Exposure via TCP 3389
Port Forwarding via SSH.EXE on Windows
Windows svchost.exe RDP (3389) Connections to HTTP/HTTPS Ports 80 or 443
Windows Plink Remote Port Forwarding via -R Command Line
Suspicious SCATTERED SPIDER Chisel Tunnel to Cloudflare Quick Tunnel (via process_creation)
Suspicious Enabling of Remote Desktop via fDenyTSConnections Registry by DeadLock Ransomware
Suspicious Cloudflared Tunnel Execution for Command and Control by Kraken Ransomware
Windows svchost RDP via Reverse SSH Loopback Tunnel to 127.0.0.0/8:3389
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.