Malicious Service Creation to Execute tscon for RDP Session Hijacking

PremiumReviewedSigma · High · v1
Product
windows
Service
system
Author
HuntRule
Published
2026-08-16
Updated
2026-08-28

ATT&CK techniques

Persistence → Lateral Movement
  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 detects registration of a Windows service whose image path invokes tscon.exe with a destination session, the mechanism adversaries use to run tscon under the SYSTEM service context and hijack an inactive Remote Desktop session. Standalone tscon execution is insufficient for this technique, so a service wrapping tscon is a strong signal of session hijacking. Legitimate services do not invoke tscon in this manner.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious RDP Session Hijack via Service Creation Abuse (via security)
Suspicious RustDesk Remote Access Service Installation via sc (via process_creation)
Malicious Service Creation Pointing to Public Data File via sc (via process_creation)
EAP Service Activation by Liontail Framework for DLL Sideloading - Via Command (via process_creation)
Malicious Service Permissions Hijacked for Privileges Abuse - Service (via process_creation)
Malicious Service Abuse with Backdoored "command Failure" - Service (via process_creation)
Malicious Service Permissions Hijacked for Privileges Abuse - Reg via Command (via process_creation)
Malicious Mimikatz Driver Registration - Reg via Sysmon (via registry_event)
Suspicious PSexec Service Installation (via security)
Malicious Service Creation to Execute tscon for RDP Session Hijacking
Pivot detection · T1543.003 · 9 related

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