huntrule

Windows: ScreenConnect Temporary File Creation in ConnectWiseControl Temp

Flags file writes to ScreenConnect’s ConnectWiseControl\Temp staging directory from ScreenConnect.WindowsClient.exe.

FreeReviewedSigma · Low · v2
Product
windows
Category
file_event
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 matches file creation events where the process image ends with ScreenConnect.WindowsClient.exe and the target filename contains the ConnectWiseControl Temp directory under the user Documents path. Attackers abusing ScreenConnect for remote execution commonly drop temporary binaries into this location before running them, so this telemetry can highlight suspicious staging activity. It relies on Windows file event logs that provide both the creating process image and the target filename.

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 Temporary File Creation in ConnectWiseControl Temp
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.