Suspicious RDP Enablement via fDenyTSConnections Registry Modification

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-01
Updated
2026-10-01

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 modification of the fDenyTSConnections registry value to zero, which enables inbound Remote Desktop connections. Akira ransomware operators toggled this value to open RDP for lateral movement across victim hosts. Enabling RDP outside of change control frequently precedes hands-on lateral movement and ransomware staging.

Related detections9 linkedT1112 — drag to rearrange
Suspicious RDP Enablement via fDenyTSConnections Registry Modification [Huntress] #2
Suspicious Enabling of Remote Desktop via fDenyTSConnections Registry by DeadLock Ransomware
Suspicious Remote Desktop Enabled via fDenyTSConnections Registry by Sandworm
Malicious Remote Desktop Enablement via Registry
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
Malicious Restricted Admin Mode Enabled for Pass-the-Hash RDP
Malicious Windows Defender Service Disable via Registry
Suspicious RDP Enablement via fDenyTSConnections Registry Modification
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.