Windows mstsc.exe launched with local .rdp file argument

Alerts on mstsc.exe executions that reference local .rdp files via the command line.

FreeReviewedSigma · Low · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems), Christopher Peacock @securepeacock (SigmaHQ), DRL 1.1
Published
2023-04-18
Updated
2026-07-30

ATT&CK techniques

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

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule flags process creation where mstsc.exe is executed with a command line ending in a local .rdp file path. Attackers can use mstsc with crafted or staged RDP connection files to initiate unauthorized remote sessions and move from initial access to command and control. It relies on Windows process creation telemetry, including the image name (or original filename) and the command line containing a .rdp argument.

Related detections9 linkedT1219 — drag to rearrange
Possible AnyDesk RMM Silent MSI Installation via Windows Installer (via process_creation)
macOS Process Creation: MeshAgent Remote Access via --meshServiceName
Windows MeshAgent Remote Access Tool Command Line Execution Indicators
Windows Process Creation: Microsoft QuickAssist.exe Execution
Windows MeshAgent remote command execution via cmd.exe or PowerShell child processes
Windows Incoming AnyDesk Connection via AnyDesk.exe or AnyDeskMSI.exe
Windows File Drop Indicators for RemoteKrbRelay SMB Relay Secret Dump Module
Windows DNS Queries to azurewebsites.net From Non-Browser Processes
Windows CSharp Streamer RAT Potentially Loaded .NET Executable from Temp dat####.tmp
Windows mstsc.exe launched with local .rdp file argument
Pivot detection · T1219 · 9 related

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