Microsoft introduces new Windows protections against RDP file phishing attacks with warnings and disabled risky shared resources by default.
| IOC Type | Value | Description | Relevant MITRE ATT&CK Techniques |
|---|---|---|---|
| Filepath | .rdp | Remote Desktop connection files used in phishing campaigns | T1566.001 |
| Threatactor | APT29 | Russian state-sponsored hacking group that has used rogue RDP files | TA0001|TA0008 |
| Code | Title |
|---|---|
| T1566.001 | Phishing: Spearphishing Attachment - Phishing - Spearphishing Attachment using malicious RDP files |
| T1021.001 | Remote Services - Remote Desktop Protocol abuse |
| T1133 | External Remote Services |
| T1056.001 | Input Capture - Clipboard Data |
| T1003.001 | Credential Access - OS Credential Dumping |
| T1021.002 | Remote Services - SMB/Windows Admin Shares |
| T1552.001 | Unsecured Credentials - Credentials in Files |
| T1187 | Forced Authentication |
| Type | Value |
|---|---|
| Sector | Enterprise |
| Sector | Government |
Microsoft has introduced new Windows protections to defend against phishing attacks that abuse Remote Desktop connection (
Educational dialog warning about the risks of RDP files Source: Microsoft Future attempts to open RDP files will now display a security dialog before any connection is made. This dialog shows whether the RDP file is signed by a verified publisher, the remote system's address, and lists all local resource redirections, such as drives, clipboard, or devices, with every option disabled by default. If a file is not digitally signed, Windows displays a "Caution: Unknown remote connection" warning and labels the publisher as unknown, indicating there is no way to verify who created the file. Windows warning that an RDP file is from an unverified publisher Source: Microsoft If the RDP file is digitally signed, Windows will display the publisher, but still warn you to verify their legitimacy before connecting. It should be noted that these new protections apply only to connections initiated by opening RDP files, not to those made through the Windows Remote Desktop client. Microsoft says that Administrators can temporarily disable these protections by going to the HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\Client Registry key and modifying the RedirectionWarningDialogVersion value so it is set to 1 . However, as RDP files have historically been abused in attacks, it is strongly recommended to keep these protections enabled.