What Huntress found in the ScreenConnect CVE-2026-84869 campaign
Attackers exploiting the ScreenConnect CVE-2026-84869 flaw have sent at least 688,000 malicious file requests to 42 managed service provider servers since October 20, and they appear to be waiting for a technician to walk in. The activity is documented in Huntress's research, which the security firm published around November 16. The story has resurfaced in this week's roundups, but the core findings are about a week old, so this is follow-up coverage of an established campaign rather than a new discovery.
Huntress described the behavior as a spray. In its write-up, the firm said: "Attackers appear to be spraying servers blindly: Since October 20, we've seen at least 688,000 guest 'run file' requests for update*.bat hit 42 MSP ScreenConnect servers from 29 IP addresses, waiting for any technician to join."
That sentence contains most of the story. The requests came from 29 source addresses. They targeted a batch file matching the pattern update*.bat, and they kept arriving for nearly four weeks, through November 16. SecurityWeek framed the activity as a month-long campaign, which fits the timeline.
How the flaw lets a guest run files on a technician's PC
ScreenConnect is a remote-support tool. MSPs use it to see and control their clients' machines, so one compromised server can reach many downstream businesses. Huntress describes CVE-2026-84869 as a client flaw that lets a guest push a file, which a connecting technician's host client then runs. Reports from Cyberpress and SecurityOnline rate the flaw CVSS 9.9 and describe it as a file-transfer authentication bypass.
The exploit path is what makes this worrying for IT teams. The attack does not require a user to click a link or accept a prompt. A technician who joins a session on a spray-targeted server can have a file executed on their own computer. That is a different risk from a conventional server breach, because the victim is the person doing the support work.
Researchers describe this as a 'relay trap', in which a malicious guest waits for a technician to arrive. It is a form of trusted-relationship abuse. The attacker does not need to break through the MSP's perimeter. They only need to sit where the vendor's tool, the MSP and the client already trust one another.
The blast radius follows the technician. If one technician's PC is taken over, the attacker can reach every customer environment that person manages. For a small MSP, that may mean every client it supports. For a business that outsources its IT, the exposure can come from a vendor it never talks to directly about security.
Which ScreenConnect versions fix CVE-2026-84869
ScreenConnect 26.6.5 and later contain the fix. One source gives the build number as 26.6.5.9742. The patch and the CVE publication both date to September 8, 2026, which means the fix has been available for more than two months as of today. Cyberpress and SecurityOnline both note that affected technician host clients and Access agents also need updating, not just the server.
| Component | What to do |
|---|---|
| ScreenConnect server | Confirm the version is 26.6.5 or later |
| Technician host clients | Update each one and verify the version on every technician machine |
| Access agents | Update as well, following the patch guidance |
Admins should not treat the server update as the whole job. A patched server with an old technician client still leaves the entry point open on the machines that matter most.
Reported compromises and what remains unconfirmed
The confirmed impact is small so far. According to SecurityOnline, Huntress saw one full compromise, one test run and the mass spray. In one case on November 12, a technician workstation was taken over in roughly nine seconds, according to a summary of the Huntress findings. Huntress has not confirmed how many customer environments were affected downstream.
A separate campaign planted crypto-themed guest sessions on more than 100 MSP servers, according to SecurityOnline. That activity differs from the file-execution spray, which suggests the threat is not limited to a single lure.
The largest number in circulation comes from Decryption Digest, which says more than 400 MSP environments were breached in four days. That figure conflicts with Huntress's count of 42 servers, and no other source I checked confirms it. USA 24 does not treat it as established.
The payload: a batch file, a Telegram bot and a rogue client
The malicious payload is a batch file that contacts a Telegram bot and installs a rogue ScreenConnect client, according to SecurityWeek and OffSeq Radar. That sequence matters for defenders. A rogue ScreenConnect client looks like a legitimate remote-support tool, so it can blend into a busy technician machine.
Telegram traffic from a support workstation is unusual for most MSPs, which makes it a useful thing to search for. Security teams should check outbound connections from technician PCs, not only from servers.
SCKit: a claim that still needs a primary source
Decryption Digest reports that Microsoft disclosed a toolkit called SCKit in November 2026. According to that report, SCKit abuses this CVE to swap the legitimate client for a rogue one, using a component it calls RelayTrap. USA 24 could not find a Microsoft primary source for that disclosure, so readers should treat the SCKit account as single-sourced.
The sources also disagree on how SCKit works. Huntress says SCKit does not directly exploit this CVE but may stage it as a 'relay trap'. Decryption Digest says SCKit does exploit the flaw. Until a primary source resolves the conflict, SCKit should be treated as a reported toolkit with unclear links to the CVE.
No source names a threat actor behind the spray. Defenders should avoid assuming a specific group until researchers publish attribution.
What MSPs and their clients should do now
For managed service providers and internal IT teams, the priorities are clear:
- Confirm that every ScreenConnect server, technician host client and Access agent runs 26.6.5 or later.
- Review guest-session and file-transfer settings, and disable anything your technicians do not need.
- Search technician machines for unexpected ScreenConnect clients, batch files such as
update*.bat, and traffic to Telegram. - Treat any session you cannot explain as a possible compromise, then review the customer environments that technician touched.
Business owners who rely on an outside MSP should ask three questions. Has the provider patched ScreenConnect? When did it update its technician clients? Has it checked technician machines for the artifacts listed above? A provider that cannot answer quickly deserves a closer look.
Fake IT support is a related lure that criminals already use. USA 24 covered the arrests of suspects tied to Chaos ransomware after fake IT support calls, which shows how valuable the help desk has become to attackers.
What to watch next
Three open questions will shape how this story develops. The first is whether CISA adds CVE-2026-84869 to its Known Exploited Vulnerabilities catalog. The sources reviewed for this story do not show an entry, so readers should check the catalog directly rather than assume a listing.
The second is whether Huntress or other researchers publish indicators or downstream customer counts that resolve the gap between 42 servers and the 400-plus figure. The third is whether Microsoft confirms SCKit, which would settle whether it is a distinct toolkit or a label that needs revision.
The pattern also echoes other recent supply-chain stories. USA 24's coverage of the Rackspace Spot breach showed how secrets in shared infrastructure can reach customer environments. Over the next few weeks, the real test will be how quickly MSPs update their technician machines, because a spray that waits for connections rewards whoever moves slowest.




