# CVE-2026-84869 in ConnectWise ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts

> Huntress confirmed in-the-wild exploitation of CVE-2026-84869 (CVSS 9.9), where a guest in a ScreenConnect Support/Access session can trigger file-transfer actions that the technician's host client processes without authorization or confirmation, including running files with elevated rights. Huntress observed a technician workstation fully compromised in about 9 seconds on 2026-11-12 and 688,000+ guest 'run file' requests across 42 MSP servers from 29 IPs since 2026-10-20.

- **Published:** 2026-11-16T22:58:16Z
- **Last reviewed:** 2026-11-16T22:58:16Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6188
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6188.png
- **ID:** TL-2026-6188
- **Severity:** CRITICAL (CVSS 9.9)
- **Category:** VULNERABILITY
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 27 (3 shown free below)
- **CVEs:** CVE-2026-84869

## Description

CVE-2026-84869 (CWE-862 Missing Authorization, CWE-269 Improper Privilege Management; CVSS 3.1 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) was disclosed by ConnectWise on 2026-09-08 in the ScreenConnect 26.6.5 security bulletin and added to the CISA KEV catalog on 2026-09-11 (federal remediation due 2026-09-14). The flaw is in the client, not the server: during an active Support or Access session, a guest can trigger file-transfer and run-file actions that the technician's host client or Access agent processes without authorization or Host confirmation, including running files with elevated rights. ConnectWise states all versions prior to 26.6.5 are affected and that ScreenConnect servers themselves are not affected, so a server-only update does not fix the issue. Huntress observed vulnerable client versions 22.x, 24.2 and 25.8 exploited in the wild.

Huntress documented a mass spray beginning 2026-10-20 and still active on three servers at publication (2026-11-16): 688,000+ guest 'run file' requests for update.bat or update_<8 hex>.bat across 42 MSP servers from 29 IPs. The busiest server saw 10 guest sessions from seven IPs make 70,414 requests. The 8-hex suffix appears to be a wave ID rather than a per-victim ID (an earlier wave used update_c99a4b29.bat). Spray sessions often have blank names or default Windows hostnames, a guest version matching the server build (25.8.3.9466 on the busiest server) and empty public keys on about half. 27 spray sessions across 17 servers had the Company property (CustomProperty1) set to 'crypto client'. Earlier, more targeted activity included a near-miss on 2026-10-19 (Run-Lateral.bat pushed seven times at a 24.2 client, 4.3 seconds after the technician disconnected), path-traversal pushes of Sync.bat into technician Startup folders on 2026-10-23, 24 and 27, a hand-operated canary (marker.txt) from 91.224.92.167, and an svc_payload.cmd push from 107.148.223.37.

On 2026-11-12 at 16:46:20-16:46:29 UTC an MSP technician workstation was fully compromised in about 9 seconds. The guest-pushed update_224ac089.bat ran from the client's Temp folder with argument xhsdf_wrwerhjf_shhdga, relaunched itself hidden via PowerShell and WScript.Shell, decoded a Base64-encoded Telegram bot token and chat ID to report the new victim, and performed recon (reg query of the Windows product name and build, a check for its own client, net session for admin rights). It then used curl (with retry and speed-limit flags) to download https://masterdarky.com/WindowsUpdate.msi to %TEMP%\wupdate_224ac089.msi and unpacked it as an administrative image with msiexec /a TARGETDIR=%LOCALAPPDATA%\wclient_224ac089 /qn, which leaves no install record. It set the seclogon service to auto-start and started it, launched the payload via runas /trustlevel:0x20000 and PowerShell Start-Process (csc.exe compiled a PowerShell Add-Type), and started a rebranded ScreenConnect client, WindowsUpdate.WindowsClient.exe, with parameters h=masterdarky.com&p=8041, connecting to the attacker's relay. No further payloads were described.

Huntress assesses with high confidence that the spray operator and the masterdarky.com operator are the same; no named threat actor is given. This activity is separate from the SCKit worm campaign (rogue clients via a vulnerable third-party server extension, reported 2026-11-11) and the fake crypto-exchange session campaign, though targeting overlapped on at least one technician. Compromise of an MSP technician workstation exposes RMM, PSA, ScreenConnect, password-vault and customer admin credentials, creating downstream customer risk. Fix: update all technician host clients and Access agents to 26.6.5 or later. Interim mitigation: remove the TransferFiles permission (formerly TransferFilesInSession) from every role.

## MITRE ATT&CK

- T1583.001 Domains
- T1608.001 Upload Malware
- T1199 Trusted Relationship
- T1203 Exploitation for Client Execution
- T1059.003 Windows Command Shell
- T1059.001 PowerShell
- T1547.001 Registry Run Keys / Startup Folder
- T1543.003 Windows Service
- T1134.002 Create Process with Token
- T1564.003 Hidden Window
- T1140 Deobfuscate/Decode Files or Information
- T1218.007 Msiexec
- T1027.004 Compile After Delivery
- T1012 Query Registry
- T1082 System Information Discovery
- T1049 System Network Connections Discovery
- T1102.003 One-Way Communication
- T1219.002 Remote Desktop Software
- T1571 Non-Standard Port

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**ScreenConnect Client Executing Guest-Pushed Batch File (CVE-2026-84869 Exploitation)** (`TL-2026-6188-SPL-001`)

Behavior-first detection of CVE-2026-84869 exploitation: a ScreenConnect host client or Access agent spawns cmd, PowerShell, WScript or mshta against a batch file in the user Temp folder, or a spray filename seen in the wild (update.bat, update_<8hex>.bat such as update_224ac089.bat, Run-Lateral.bat, Sync.bat, svc_payload.cmd, marker.txt, argument xhsdf_wrwerhjf_shhdga). Missing authorization lets a guest trigger run-file with no Host confirmation (T1203, T1199).

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1203, T1199, T1059.003
- **Data sources:** sysmon, microsoft_defender_endpoint
- **Severity:** critical
- **Confidence:** high

### Splunk SPL

```spl
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
  (ParentImage="*\\ScreenConnect.ClientService.exe" OR ParentImage="*\\ScreenConnect.WindowsClient.exe" OR ParentImage="*\\ScreenConnect.WindowsBackstageShell.exe")
  (Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe" OR Image="*\\wscript.exe" OR Image="*\\cscript.exe" OR Image="*\\mshta.exe")
| eval ioc_hit=if(match(CommandLine,"(?i)(update(_[0-9a-f]{8})?\\.bat|Run-Lateral\\.bat|Sync\\.bat|svc_payload\\.cmd|marker\\.txt|xhsdf_wrwerhjf_shhdga)"),1,0)
| eval from_temp=if(match(CommandLine,"(?i)\\\\AppData\\\\Local\\\\Temp\\\\.*\\.(bat|cmd)"),1,0)
| stats count min(_time) as first_seen max(_time) as last_seen values(CommandLine) as command_lines values(Image) as child_images max(ioc_hit) as ioc_hit max(from_temp) as from_temp by host, User, ParentImage
| where ioc_hit=1 OR from_temp=1
| convert ctime(first_seen) ctime(last_seen)
```

### Microsoft KQL

```kql
let ScreenConnectClients = dynamic(["ScreenConnect.ClientService.exe", "ScreenConnect.WindowsClient.exe", "ScreenConnect.WindowsBackstageShell.exe"]);
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ (ScreenConnectClients)
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe")
| extend IocHit = ProcessCommandLine matches regex @"(?i)(update(_[0-9a-f]{8})?\.bat|Run-Lateral\.bat|Sync\.bat|svc_payload\.cmd|marker\.txt|xhsdf_wrwerhjf_shhdga)"
| extend FromTemp = ProcessCommandLine matches regex @"(?i)\\AppData\\Local\\Temp\\.*\.(bat|cmd)"
| where IocHit or FromTemp
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, IocHit, FromTemp
```

### Sigma

```yaml
title: ScreenConnect Client Spawns Script Interpreter Running Guest-Pushed Batch File (CVE-2026-84869)
id: 3f1c7a52-8b6e-4d2a-9c41-6e0b5a7d1f10
status: experimental
description: Detects a ScreenConnect host client or Access agent spawning cmd, PowerShell, WScript or mshta against a batch file in Temp or a known CVE-2026-84869 spray filename such as update_<8hex>.bat, Run-Lateral.bat, Sync.bat, svc_payload.cmd or marker.txt. A guest session can trigger run-file actions on the technician client without Host confirmation.
references:
  - https://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation
  - https://www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin
author: Threadlinqs Team
date: 2026/11/16
tags:
  - attack.initial-access
  - attack.t1199
  - attack.execution
  - attack.t1203
  - attack.t1059.003
  - cve.2026.84869
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|endswith:
      - '\ScreenConnect.ClientService.exe'
      - '\ScreenConnect.WindowsClient.exe'
      - '\ScreenConnect.WindowsBackstageShell.exe'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\mshta.exe'
  selection_ioc:
    CommandLine|re: '(?i)(update(_[0-9a-f]{8})?\.bat|Run-Lateral\.bat|Sync\.bat|svc_payload\.cmd|marker\.txt|xhsdf_wrwerhjf_shhdga)'
  selection_temp:
    CommandLine|re: '(?i)\\AppData\\Local\\Temp\\.*\.(bat|cmd)'
  condition: selection_parent and selection_child and (selection_ioc or selection_temp)
falsepositives:
  - Technicians legitimately transferring and running a script in a support session
  - Authorized RMM automation that stages .bat or .cmd files through ScreenConnect
level: high

```

**Known false positives:**

- Technicians legitimately transferring and running a script in a support session
- Authorized RMM automation that stages .bat or .cmd files through ScreenConnect

**Tuning notes:** Exclude known-good internal script names and technician accounts after baselining; keep the update*.bat / Run-Lateral / Sync / svc_payload / marker names as always-alert. Raise to a page when the parent client version is below 26.6.5. Extend the parent list if your fleet uses renamed ConnectWise Control binaries.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- ScreenConnect Client Drops Startup-Folder Payload or Spray Filename (CVE-2026-84869) (locked: unlock with TL Creds)
- Post-Exploitation Recon and Stage-2 Download Chain (reg query, net session, curl MSI, msiexec /a) (locked: unlock with TL Creds)
- Rogue Rebranded ScreenConnect Client WindowsUpdate.WindowsClient.exe Execution (locked: unlock with TL Creds)
- Hidden Relaunch of Guest-Pushed Batch via PowerShell and WScript.Shell (locked: unlock with TL Creds)
- Silent Msiexec Administrative Unpack (wupdate_*.msi to wclient_*) and Runas Trustlevel 0x20000 (locked: unlock with TL Creds)
- Script Interpreter or curl Reporting to Telegram Bot API (Victim Beacon) (locked: unlock with TL Creds)
- Seclogon Service Change, Runas Low-Trust Launch and PowerShell csc Compile Correlation (locked: unlock with TL Creds)
- C2: [indicator] ScreenConnect Relay (Port 8041), [indicator] and Known Spray Guest IPs (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (3 of 27)

Defanged, TLP:CLEAR.

- IP address: `194.15.36[.]33`
- Domain: `masterdarky[.]com`
- File hash: `f8871b1561d5c77c297378a7f49c84de52a01ff297395544f0e95d13ef972841`

Full set of 27 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [CVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts (Huntress)](https://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation)
- [ConnectWise Security Bulletin: ScreenConnect 26.6.5](https://www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin)
- [CVE Record CVE-2026-84869](https://www.cve.org/CVERecord?id=CVE-2026-84869)
- [NVD - CVE-2026-84869](https://nvd.nist.gov/vuln/detail/CVE-2026-84869)
- [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)
- [ConnectWise ScreenConnect CVE-2026-84869 KEV (Rescana)](https://www.rescana.com/post/connectwise-screenconnect-cve-2026-84869-kev)
- [Huntress Rapid Response: Rogue ScreenConnect Installations](https://www.huntress.com/blog/rogue-screenconnect-installations)
- [Huntress Rapid Response: SCKit Worm and Rogue ScreenConnect](https://www.huntress.com/blog/sckit-worm-rogue-screenconnect)
- [Huntress: Fake Crypto Exchange Sessions in ScreenConnect](https://www.huntress.com/blog/fake-crypto-exchange-sessions-screenconnect)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6188
