huntrule

Windows ScreenConnect Installation Execution via Remote Access Parameters

Flags Windows executions of ScreenConnect with remote access command-line parameters indicating remote session setup.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-02-11
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Initial Access → Persistence

  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 matches Windows process creation events where the command line contains ScreenConnect-specific remote access parameters (e=Access, y=Guest, and p=, c=, k=). Attackers commonly use remote access tooling to establish interactive control and persistence after initial access. The detection relies on process creation telemetry, specifically the full command-line string in process start events.

Reporting behind it

Related detections9 linkedT1133 — drag to rearrange
Suspicious SonicWall NetExtender VPN Command-Line Authentication with Always-Trust (via process_creation)
Suspicious Reverse SSH Tunnel Creation with Host Key Verification Disabled (via process_creation)
Suspicious Shell Script Execution From Temp Directory on SonicWall SMA1000 Appliance (via process_creation)
Possible PAN-OS CVE-2026-0257 Exploitation via GlobalProtect PoC Artifacts (via network)
Possible RD Web Access Brute Force via Repeated Login POST Requests
Suspicious Security Group Ingress Rule Opened to the Internet via CloudTrail
SplashTop Network
Suspicious SoftEther VPN Hamcore Config Written to ProgramData (via file_event)
SplashTop Process
Windows ScreenConnect Installation Execution via Remote Access Parameters
Pivot detection · T1133 · 9 related

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