huntrule

Windows ScreenConnect RMM System Command Execution via cmd.exe

Flags cmd.exe launched by ScreenConnect.ClientService.exe with a TEMP\ScreenConnect command-line path.

FreeReviewedSigma · Low · v1
Product
windows
Category
process_creation
Author
Ali Alwashali (SigmaHQ), DRL 1.1
Published
2023-10-10
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Execution

  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. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects Windows process creation where ScreenConnect.ClientService.exe launches cmd.exe (or cmd.exe by name) and the command line includes a TEMP folder path containing "ScreenConnect". Attackers may use ScreenConnect to execute arbitrary commands on remote endpoints under the guise of legitimate remote management. The detection relies on process creation telemetry capturing the parent image, the child image/original filename, and the command-line string.

Reporting behind it

Related detections9 linkedT1059.003 — drag to rearrange
Suspicious IP Release and Renew via Minimized cmd During Driver Install
Malicious IIS Worker Spawning nslookup via WS_FTP Deserialization
Malicious Metasploit Reverse Shell Injection in SQL Server (via process_creation)
Suspicious Fake Crypto Wallet Installer Batch Script Staging (via file_event)
Obfuscated Encoded PowerShell Payload Deployed via Process Execution (via process_creation)
Operator Bloopers Cobalt Strike Modules
Malicious KB Document Masqueraded Executable Spawned by Script Interpreter via RoKRAT Loader (via process_creation)
Malicious SCMBanker ClickFix Payload Fetch via Curl Piped to Cmd
Malicious Payload Assembly via MZ Header Prepend and copy Concatenation (via process_creation)
Windows ScreenConnect RMM System Command Execution via cmd.exe
Pivot detection · T1059.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.