Windows Registry: RDP PortNumber changed from default 3389

Alerts on Windows registry updates to the RDP-Tcp PortNumber when it changes away from default 3389.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-01-01
Updated
2026-07-30

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies changes to the RDP server’s configured listening port by monitoring the registry value that sets Terminal Server RDP-Tcp PortNumber. Attackers may modify the default port to make Remote Desktop Services harder to find or to evade basic detections focused on 3389. It relies on Windows registry set telemetry and matches when the port value is changed to a value other than the default 3389 (0x00000d3d).

Related detections6 linkedT1547.010 — drag to rearrange
SystemNightmare by GentilKiwi - External Printer Mapped - CVE-2021-1675 / CVE-2021-34527 (via security)
Malicious Print Spooler Privilege Escalation via Printer Added - CVE-2020-1048 (via powershell)
SystemNightmare by GentilKiwi - New External Device Added - CVE-2021-1675 / CVE-2021-34527 (via security)
Windows Process Creation: Suspicious secedit.exe Security Policy Export or Configuration
Registry Modification for UAC Bypass via Event Viewer Command Handler (Windows)
Windows Registry: Add Print Port Monitor DLL Persistence
Windows Registry: RDP PortNumber changed from default 3389
Pivot detection · T1547.010 · 6 related

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