1. Basic Information
- Article Title: CVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts
- Publisher: Huntress
- Publication Date: 2026-11-17
- Collection Date: 2026-11-18T08:00:28+09:00
- Source: Huntress
- Related Sources: SecurityWeek, ConnectWise advisory
- Related CVE: CVE-2026-84869
- Severity (Author Priority): Critical
- Basis for Severity: Huntress confirmed that 688,000 file-execution requests were sprayed across 42 MSP servers. On one technician workstation on November 12, a batch file notified a Telegram bot, downloaded an MSI, and launched a rogue ScreenConnect client in about nine seconds.
2. Quick Summary
Attackers flood run requests for update*.bat from guest sessions. If a technician using a vulnerable host client connects to the session, files may be transferred and executed without confirmation prompts.
3. Attack Flow
These are separate paths targeting the same client vulnerability and do not indicate a strict A-to-B-to-C sequence or the exact same operator. Sources are based on Huntress observations.
Attack Path A: Spraying update*.bat
- An attacker joins a session as a guest and repeatedly sends run requests for
update*.bat. - When a technician using a vulnerable host client connects, the batch file sent from the guest side can execute without prompting for confirmation.
- On one endpoint on November 12, the batch file sent a notification to Telegram, retrieved an MSI from
masterdarky[.]com, and launched a malicious ScreenConnect client in about nine seconds.
Attack Path B: Canary via marker.txt
- A guest sends
marker.txtto a connected technician. - On one endpoint on November 13, the host client opened the file and launched Notepad++. No subsequent payload was observed.
Attack Path C: Path Traversal Attempt Targeting the Startup Folder
- The attacker joins an active customer support session as an additional guest.
- They send a run request for
../../../AppData/Roaming/Microsoft/Windows/STARTM~1/Programs/Startup/Sync.bat. - If a Windows client accepts the path and writes the file to the Startup folder, the file could run at the next logon. Successful placement and persistence remain unconfirmed, and the Windows path failed on Mac clients.
4. Attacker Position and Execution Location
- Remote attackers targeting MSP technician host clients from the guest side of ScreenConnect.
5. Victim and Administrator Perspectives
- Victims: Technicians simply connect to the session as usual, potentially without any file execution prompts appearing.
- Administrators: Can observe RanFiles in the server database, batch files and PowerShell executed from the host client's Temp directory, and processes or connections associated with unauthorized ScreenConnect clients.
6. Success and Failure Conditions
- Success Conditions: Host client version prior to 26.6.5, a session containing an attacker guest, technician connection, and a successful file execution path.
- Failure Conditions / Mitigations: Update host clients and Access agents to version 26.6.5 or later, and temporarily disable the TransferFiles permission.
7. What Happens Upon Success
- Code execution on technician workstations, deployment of unauthorized RMM tools, and potential spillover to MSP credentials and customer access.
8. Observable Logs
- Email: No specific notes.
-
Proxy / SWG / DNS: Traffic to Telegram bots,
masterdarky[.]com, and attacker ScreenConnect relays. -
Endpoint EDR: Execution of
update*.batfrom the Temp directory, PowerShell, WScript, installers, and rogue clients originating from ScreenConnect host clients. - Identity IdP: Technician accounts and the use of ScreenConnect guest sessions.
- SaaS Cloud: RanFiles (EventType 85) / SentFiles (86), session participation, guest requests, and client versions.
- Network: High volume of run requests from 29 source IPs and connections to unauthorized relays.
9. Attack Success Assessment
- Path A Public Info: The 688,000 requests sent to 42 MSP servers represent exploit attempts. On one endpoint on November 12, the launch of a batch file and a rogue client was confirmed. Impact on customer environments remains unconfirmed.
-
Path B Public Info: On one endpoint on November 13,
marker.txtwas confirmed to open via Notepad++. Whether the file ran on another technician's endpoint in October is unknown. - Path C Public Info: Startup paths were confirmed sent to three technicians in October. Successful placement or execution on the next login was unconfirmed on Windows, and the path failed on Mac.
10. Investigation Playbook
-
Trigger: Run requests for
update*.bat, scripts in the host client's Temp directory, and traffic related to Telegram and IOCs. - Initial Checks: Identify servers, sessions, guests, technicians, client versions, and initial requests.
- Endpoint: Preserve process trees, Temp directories, installers, services, and ScreenConnect configurations.
- Identity Cloud: Check technician credentials, RMM sessions, and customer access.
- Follow-On: Track unauthorized relays, saved credentials, RMM consoles, and access to customer endpoints.
- Containment: Terminate sessions, update clients, revoke permissions, isolate or reimage workstations, and rotate credentials.
- Classification: Separate and categorize spray requests, technician connections, file execution, unauthorized RMM connections, and customer environment spillover.
11. Defense and Detection Ideas
- Single Event: Execution of batch files, PowerShell, or WScript from the ScreenConnect host client.
- Time Series: Correlate guest run requests -> technician participation -> Temp files -> rogue RMM connections.
-
Hunting: Search for
update*.bat,masterdarky[.]com, Telegram, and clients masquerading as Windows Update. - Logging Gaps: Server-side request logs alone cannot prove successful execution on technician hosts.
- Priority Controls: Prioritize updating all host clients and Access agents to version 26.6.5 or later.
12. Facts / Inference / Hypothesis
Facts
- Between October 20 and November 16, 2026, 42 MSP servers, 29 source IPs, and 688,000 run requests were observed.
- CVE-2026-84869 has a CVSS score of 9.9, affecting clients prior to version 26.6.5, while servers themselves are not affected.
- Huntress distinguishes this activity from the campaign involving unauthorized guest sessions disguised with cryptocurrency exchange names, reported on November 13.
Inference
- Repeated requests represent a probabilistic spray awaiting technician connections, and the total request count should not be treated as the number of victims.
Hypothesis
No additional hypotheses. Unconfirmed items are listed under Unknowns and Further Investigation.
13. MITRE ATT&CK Mapping
| ID | Technique | Confidence | Basis |
|---|---|---|---|
| T1203 | Exploitation for Client Execution | high | Technician clients executed or opened guest-pushed files in Paths A and B, rather than exploiting a server vulnerability. Source |
| T1105 | Ingress Tool Transfer | high | Path A involved retrieving batch files from guests and MSIs from external hosts. Source |
| T1219 | Remote Access Software | high | Rogue ScreenConnect clients launched in Path A; customer spillover unconfirmed. Source |
| T1059.001 | Command and Scripting Interpreter: PowerShell | high | Batch files launched hidden PowerShell instances in Path A. Source |
14. Unknowns and Further Investigation
- The identity of the attackers, the full list of compromised hosts, credential access, and the scope of impact on customer endpoints remain unknown.
- The total number of the 688,000 observed requests that actually resulted in execution remains unknown.
15. Impact on SOCs and Organizations
MSPs and help desks should not assume that patching servers alone is sufficient; verify technician host client and Access agent versions, active guest sessions, and RanFiles.
16. Summary by Target Audience
- For SOCs: Correlate process and network artifacts on server sessions and technician endpoints across the same timeline.
- For Administrators: Update to version 26.6.5 or later and restrict connections from older client versions. Until clients are updated, disable the TransferFiles permission as a temporary mitigation.
- For Users: Because technicians can be affected even during normal support sessions, use only organization-approved sessions.
Top comments (0)