$RodHat_/search
MOTD

SCKit: ScreenConnect worm tries CVE-2026-84869 on technicians

Published by

This article may contain Amazon affiliate links. I may earn a commission if you buy through them. Disclosure.

Editorial card for the SCKit ScreenConnect worm
Editorial card: RodHat

Attackers broke into cloud-hosted ConnectWise ScreenConnect environments this week and pushed rogue ScreenConnect clients to customer endpoints. Researchers then pulled apart the toolkit they left behind. It’s called SCKit, and the interesting part is that it tries to turn a support session around and hit the technician who opened it.

The mechanism is CVE-2026-84869, a ScreenConnect client bug. NVD and ConnectWise describe it as missing authorization (CWE-862): file transfers can be processed through an active session without authorization or Host confirmation, including elevated execution. CVSS 3.1 is 9.9, AV:N/AC:L/PR:L/UI:N/S:C. ConnectWise fixed it in 26.6.5 on September 8, 2026. ScreenConnect servers aren’t affected. The clients are.

Per BleepingComputer’s write-up of the Huntress and Blackpoint Cyber analyses, SCKit is 16 scripts and components. One piece, RelayTrap, replaces the legitimate Guest process on an infected endpoint and waits for a technician to connect. It then tries to send a file the wrong way, from customer to technician, and have it run. A C# source file gets downloaded and compiled locally by PowerShell, so there’s no prebuilt binary to sign-match. Other components go after the technician’s browser cookies for the ScreenConnect session, then walk the technician’s permissions and spread through the Shared Toolbox. Customer endpoint to tech workstation to every other customer that tech can reach. That’s the worm part, and it’s a good design. Ugly, but good.

It reportedly doesn’t work. Blackpoint says the exploit failed against a patched client: “The Guest side queued the transfer, but the current client never requested or ran the payload.” Huntress says the console takeover failed in every recovered host log it examined. Nobody has seen the worm spread. That holds only for clients at 26.6.5 or later.

How they got in is a separate and dumber story. Huntress points at RMM+, a third-party ScreenConnect extension. Versions 1.0.31 and 1.0.32 accept a blank access key if the admin never set one, so an attacker supplies an empty key and runs commands with no login and no MFA. Huntress counts at least 288 endpoints across 48 organizations hit inside 90 minutes. ConnectWise says it found about 400 partner environments with RMM+ family extensions, disabled them in the cloud ones, and stresses that having the extension isn’t proof of compromise. ConnectWise also says it has found no evidence that initial access involved a ScreenConnect vulnerability. Its investigation is still open as of the November 12 update.

I’ll say what I always say about remote-management stacks: you are running a root-equivalent backdoor on every customer machine and calling it a product. An empty string passing an auth check is a 1990s bug. Reading the advisory, the vendor’s own list of damage control is longer than the original sin.

What ConnectWise says to do:

  1. Update every technician client to 26.6.5 or later. Updating the cloud console does not update technician clients, so check the version on each workstation.
  2. Until then, remove the Transfer Files permission (older builds call it TransferFilesInSession) from roles’ session groups.
  3. Keep the identified extensions disabled. On-prem shops have to do this themselves.
  4. Revoke all active ScreenConnect web sessions and identity-provider sessions from a trusted device, reset credentials, enforce MFA. A password reset alone doesn’t kill existing sessions.
  5. Don’t investigate with ScreenConnect. Use EDR or another out-of-band path, and include technician workstations that connected to affected machines.
  6. Review authentication, extension install, Run Command and Toolbox logs before you wipe anything.

None of this is a Unix problem, but the lesson is the old one: if your management plane can push code to every endpoint, it’s the target. Keep it small and keep it off the open internet; the sandboxing hub covers how to cut privileges down, and the kernel and security hub has the rest of this month’s carnage, including yesterday’s Chrome zero-day. Go check your client versions.

Sources

  1. CVE-2026-84869 (NIST National Vulnerability Database)
  2. CVE-2026-84869 disclosure (ConnectWise)
  3. ScreenConnect security advisory (ConnectWise Trust Center)
  4. New worm-like 'SCKit' malware targets MSPs in ScreenConnect attacks (BleepingComputer)