huntrule

Windows ScreenConnect Remote Command Execution (EventID 200)

Detects ScreenConnect command execution on Windows by matching EventID 200 with an 'Executed command of length' message.

FreeReviewedSigma · Low · v2
Product
windows
Service
application
Author
Ali Alwashali (SigmaHQ), DRL 1.1
Published
2023-10-10
Updated
2026-07-31
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 identifies ScreenConnect events where a remote command execution message is present (EventID 200) and the event payload includes the text 'Executed command of length'. This matters because attackers who gain access to an environment may leverage legitimate remote admin tooling to run commands covertly. It relies on Windows application logs containing the ScreenConnect provider name, event ID, and the specific command execution string in the event data.

Reporting behind it

Related detections9 linkedT1059.003 — drag to rearrange
Possible Apache ActiveMQ Exploitation via Java Spawning Command Shell (via process_creation)
Suspicious Doenerium Host Fingerprinting via cmd.exe
Suspicious Scheduled Task Creation Referencing dllFake Batch Scripts (via process_creation)
Suspicious Backup Exec Remote Agent Spawning Command Shell via Process Creation (via process_creation)
Suspicious ClickFix Command Execution via RunMRU Registry Key
Suspicious LampoRAT Command Dispatcher via Cmd Delayed Expansion Flags (via process_creation)
Malicious WSUS Service Spawning Command Shell via CVE-2025-59287 (via process_creation)
Malicious SharePoint w3wp Spawning Command Shell and PowerShell
Suspicious extrac32 CAB Extraction Abuse
Windows ScreenConnect Remote Command Execution (EventID 200)
Pivot detection · T1059.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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