On Friday we told you about attackers abusing a ScreenConnect add-on (RMM+). Huntress published a different and more direct attack on Monday. Attackers are using CVE-2026-84869, a ScreenConnect flaw fixed in September, to run files on managed service provider technicians’ own PCs.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
On November 12, one technician joined a session and had a rogue remote-access client running about nine seconds later. The technician never saw a prompt. Updating the ScreenConnect server doesn’t help, because the weak spot is the client on the technician’s machine.
Huntress has confirmed attacks on ScreenConnect CVE-2026-84869: a guest in a session can push a file and the technician’s client runs it. Update every technician client to 26.6.5 and hunt first.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Attackers are using ScreenConnect’s file-transfer flaw against MSP technicians
ConnectWise fixed CVE-2026-84869 on September 8 in ScreenConnect 26.6.5, and CISA added it to the exploited catalog on September 11. A guest in a session can send file-transfer actions that the technician’s host client carries out without asking, including running the file.
- November 12: a guest-pushed
update_224ac089.batran on a technician’s PC. About nine seconds later a rebranded ScreenConnect client named after Windows Update was connected to the attacker’s relay. - Spray: between October 20 and November 16, Huntress counted 688,000 guest “run file” requests for
update.bat-style files on 42 MSP ScreenConnect servers, from 29 IP addresses. - November 13: a harmless
marker.txtwas pushed to a second technician, a test that proved the trick worked. - October: an attacker asked a technician’s client to write
Sync.batinto the Startup folder with a path-traversal trick.
Technicians’ host clients, and every customer they can reach
An MSP technician’s workstation holds consoles, saved passwords and access to every customer’s systems. Huntress says many technicians were still on 22.x, 24.2 and 25.8 clients weeks after the fix shipped. A technician who joins one unattended or look-alike session can hand over everything they can reach.
The attackers are casting wide: the spray files are named the same across servers, and guest sessions sit waiting for any technician to join. This is the second ScreenConnect warning in a week, but the earlier RMM+ problem was a server-side add-on. This one needs no extension and no login on the server side. CISA and Huntress confirm exploitation.
Update every technician client to 26.6.5, then hunt
- Update every technician’s ScreenConnect host client, and Access agents, to 26.6.5 or later. ConnectWise’s bulletin says to reinstall host clients and update Access agents after upgrading.
- If you can’t update today, remove the
TransferFilespermission from every role and session group (Administration, Security, Roles). ConnectWise lists this as a temporary measure. - Delete blank-named guest sessions that keep asking to run
update*.bat. Huntress says they come back, so check again. - Restrict who can join as a guest, and don’t join unattended sessions you can’t tie to a customer.
- If you find a hit, isolate the technician’s PC and rotate every credential that was reachable from it: RMM, PSA, password vault, ScreenConnect and customer admin accounts.
Forward this
For whoever manages our IT provider relationship: attackers are using a ScreenConnect flaw to run malware on the PCs of IT support technicians, and a technician’s PC reaches every customer they support. If we use ScreenConnect, or our IT provider does, can we ask that every technician client is on version 26.6.5 or newer, and ask whether they have checked for the signs Huntress lists?
Details
- CVE-2026-84869: improper privilege management and missing authorization in the ScreenConnect client (CWE-269, CWE-862). Published September 8, 2026. CVSS 3.1: 9.9. Affected: ScreenConnect before 26.6.5. Servers are not impacted, clients are.
- CISA KEV: added 2026-09-11, due 2026-09-14, forensic triage required.
- Huntress: blog post dated November 16, 2026. Observed November 12 (9-second compromise), November 13 (canary file), October 19 to 27 (near-miss, path traversal) and the 688,000-request spray from October 20.
- Indicators:
masterdarky[.]comrelay on port 8041;WindowsUpdate.WindowsClient.exe;%LOCALAPPDATA%\wclient_<8hex>;%TEMP%\wupdate_<8hex>.msi; a Telegram bot for reporting. - Exploitation: CONFIRMED (CISA KEV, Huntress telemetry).
Hunt / verify
- On the server (work on a copy of
App_Data\Session.db), look for eventsRanFiles(85) orSentFiles(86) from a guest connection, especiallyupdate*.bat,marker.txt,Run-Lateral.bat,svc_payload.cmdor any path containing../. Then check whether a technician’s host connection was open at the time. - On technician PCs, look for the ScreenConnect client running .bat, .cmd, .ps1, .vbs or .js files from
Documents\...\Temp\. - Look for unfamiliar files in
%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\, and for any ScreenConnect client whose command line points at a relay that isn’t yours.
Source: Huntress write-up; ConnectWise bulletin
Sources
- Huntress: CVE-2026-84869 in ScreenConnect exploited to run malicious files on MSP technician accounts
- ConnectWise: ScreenConnect 26.6.5 security patch bulletin (2026-09-08)
- SecurityWeek: MSP ScreenConnect servers targeted in month-long campaign
- NVD: CVE-2026-84869
- CISA: Known Exploited Vulnerabilities Catalog
- CyberExperts: ScreenConnect RMM+ extension attacks (November 13)
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.