Malicious Remote Desktop Enablement via Registry

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-07-28
Updated
2026-08-28

ATT&CK techniques

Persistence → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects the fDenyTSConnections value being set to 0, enabling inbound Remote Desktop connections on a host. During KawaLocker deployment this was combined with firewall disabling to open interactive access for lateral movement. Enabling RDP on servers or endpoints that normally block it expands the attacker foothold.

Related detections9 linkedT1112 — drag to rearrange
Suspicious Remote Desktop Enabled via fDenyTSConnections Registry by Sandworm
Enabling RDP service via reg.exe command execution
Suspicious LocalAccountTokenFilterPolicy Enabled via Registry (UAT-7237)
Windows reg.exe Used to Modify RDP Terminal Server Registry Values
Suspicious Plink SSH Tunnel Execution (via process_creation)
Malicious Gh0stBins RAT Registry Marker HHClient
Suspicious PebbleDash C2 Configuration Stored Under WMI Security Key (via registry_set)
Suspicious WDigest UseLogonCredential Enablement for Plaintext Credential Theft (via registry_set)
PowerShell Storing an Encoded Payload in the Registry (via process_creation)
Malicious Remote Desktop Enablement via Registry
Pivot detection · T1112 · 9 related

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