ConnectWise urges ScreenConnect client updates as SCKit targets technicians
Microsoft, Huntress and Blackpoint have analysed the toolkit used against MSPs. It is built to jump to technicians, but researchers say they have not seen that work.
Key takeaways
- ConnectWise says every ScreenConnect technician client needs the Sept. 8 security update, which blocks SCKit's attempted spread to technicians.
- SCKit's RelayTrap component tries to push a file onto a technician's computer when they connect to an infected device, using CVE-2026-84869.
- If that worked, the toolkit is designed to steal console session cookies and spread to every device the technician can reach.
- Huntress and Blackpoint say they have not seen the spread to technicians succeed, and Blackpoint found no bypass of the fix.
- Researchers advise investigating suspect devices with separate tools, not ScreenConnect sessions.
ConnectWise is telling every ScreenConnect partner to make sure each technician's ScreenConnect client has the Sept. 8 security update or a later version, after researchers found that the toolkit used in this week's attacks on managed service providers (MSPs) is built to spread to the support staff who connect to infected machines. ConnectWise says that update, which fixed a flaw tracked as CVE-2026-84869, blocks the toolkit's attempt to move from an infected endpoint to a technician.
The warning follows detailed analyses of the toolkit, called SCKit, by Microsoft Threat Intelligence, Huntress and Blackpoint Cyber. Microsoft says it has confirmed the activity ConnectWise reported and has seen attackers use ScreenConnect to install unauthorized remote-access clients and SCKit on endpoints managed by ConnectWise customers.
What happened earlier in the week?
From about 17:47 UTC on Nov. 11, an attacker used access to cloud-hosted ScreenConnect panels run by MSPs to push commands to customer devices, Huntress and Field Effect report. Huntress counts at least 288 affected hosts across 48 organizations that use its services. Huntress believes the entry point was RMM+, a third-party ScreenConnect extension; two versions of it would accept an empty access key if an administrator had never set one, according to Huntress, BleepingComputer and Microsoft. Microsoft and Field Effect note that ConnectWise is still investigating how the attackers got in, and Blackpoint says it found no technical link between the extensions and SCKit's code and calls their role in the first access an open question. ConnectWise says it has found no evidence that its own infrastructure was compromised or that initial access involved a ScreenConnect vulnerability. ConnectWise disabled five extensions in about 400 partner environments that had at least one of them, BleepingComputer and Field Effect report; ConnectWise says having them installed does not by itself mean an environment was compromised.
How is SCKit meant to reach technicians?
SCKit includes a component called RelayTrap, which replaces the normal ScreenConnect client on an infected customer device, according to Microsoft, Blackpoint and BleepingComputer. When a technician opens a support session to that device, RelayTrap tries to send a file back to the technician's computer and have it run, the reverse of a normal support transfer. Huntress and Blackpoint say the attempt starts about 2.5 seconds into the session. Blackpoint and BleepingComputer report that the technique relies on CVE-2026-84869, which affects the technician-side client, not the management server.
If that step worked, other SCKit scripts would look for ScreenConnect login cookies in the technician's Chrome, Edge or Opera browser, Microsoft says, and use them to take over the technician's management console without a password or a new MFA prompt, according to BleepingComputer. From there, the toolkit is designed to push its payload to every other device that technician can reach, which could include machines at other customers, Microsoft, Huntress and BleepingComputer report. Huntress and BleepingComputer say parts of the code, including RelayTrap, appear to have been written with help from a large language model. Blackpoint found coding flaws, including one in the cookie-reading routine, that make parts of this chain less reliable than its design suggests.
Has the spread worked?
Not so far, the researchers say. Huntress says every console-takeover attempt it found in the host logs it recovered had failed, and that it has not seen a successful jump from an infected device to a technician or onward. Blackpoint says it ran the recovered exploit against a current ScreenConnect client and the technician's side never requested or launched the file, and that it found no sign of a way around ConnectWise's fix. Microsoft describes the onward spread as the toolkit's design rather than a confirmed chain of infections.
The attacks on endpoints did happen: Field Effect says researchers saw compromised hosts reinfected soon after they were put back into service. On Nov. 13, Huntress reported a further wave of infected hosts; in one incident a rogue client posed as a Windows update service. Blackpoint says that wave appears to target on-premises ScreenConnect servers, likely with a modified version of the toolkit, and ConnectWise's advisory points to on-premises environments where the listed extensions are still enabled.
What should MSPs do?
ConnectWise and Microsoft say updating the server or cloud console does not update technician clients, so each technician's installed version must be checked. Both say the five extensions should stay disabled; on-premises partners must turn them off themselves, according to ConnectWise. Microsoft, Huntress, Field Effect and ConnectWise all advise against using ScreenConnect to investigate a suspect device, because an interactive session is what RelayTrap waits for, and recommend separate response tools instead. Microsoft, Huntress and ConnectWise also advise treating any technician workstation that already connected to an affected device as possibly exposed, reviewing Run Command and Toolbox history, and revoking ScreenConnect sessions from a clean device. Microsoft adds that deleting the rogue client alone does not remove SCKit's persistence or invalidate exposed web sessions. ConnectWise and Blackpoint also advise keeping the clients on managed endpoints up to date.
Questions readers are asking
What is SCKit?
A malware toolkit deployed in the attacks on MSPs' ScreenConnect panels that began on Nov. 11. It installs rogue ScreenConnect clients and includes code designed to spread to technicians who connect to infected devices.
Which ScreenConnect update blocks the spread to technicians?
ConnectWise says technician clients with the security update released on Sept. 8, or any later version, block the toolkit's endpoint-to-technician technique. Updating the server or cloud console does not update those clients.
Has SCKit infected any technicians?
Huntress and Blackpoint say they have not seen it succeed, and Microsoft describes the onward spread as the toolkit's design rather than a confirmed chain of infections.
Sources
- ConnectWise: ScreenConnect security advisory
- Microsoft: SCKit abuses ScreenConnect to deploy remote access and target technician sessions
- Huntress: SCKit Worm Installs Rogue ScreenConnect Clients and Session Cookie Relays Across Hundreds of Endpoints
- Blackpoint Cyber: ScreenConnect Attack: SCKit Turns Remote Support Into an Attack Platform
- BleepingComputer: New worm-like 'SCKit' malware targets MSPs in ScreenConnect attacks
- Field Effect: SCKit campaign targets MSP ScreenConnect environments
- #screenconnect
- #connectwise
- #sckit
- #msp
- #malware
Get the day's top AI & tech stories on WhatsApp: Follow the NextFish channel
Get stories like this every morning.
Related
Cybersecurity3 min
Landmark Group says Shukran loyalty members' personal data was accessed
Names, contact details and dates of birth were involved, the Dubai retailer says, but not card details, passwords or points. It has not said how many members were affected.
Cybersecurity3 min
Operation Endgame takes down Gootloader, CastleRAT and StealC servers
The Justice Department says Gootloader infected at least 25,000 computers and was used against at least 44 US ransomware victims. Europol counts 235 servers hit in all.
Cybersecurity2 min
TSMC says leaked employee data matches records at a cloud provider
The chipmaker says its own systems show no sign of compromise after a seller offered a 6.9GB file of employee records on hacker forums for three bitcoin.
Cybersecurity4 min
Cursor says key exposed at Fireworks led to malicious Claude Code extension
Cursor's incident report says attackers used stolen credentials to reach some SaaS tools and customer data, then planted a tampered extension up to 5,000 users may have received.