On this page (7 sections)
Researchers at Blackpoint Cyber report that a toolkit called SCKit turns ScreenConnect support sessions into a path from a compromised managed endpoint to the technician who connects to it. According to The Hacker News, the toolkit uses a known, already patched flaw, CVE-2026-84869, and not a new vulnerability.
If you run ScreenConnect, manage client systems through it, or are an MSP or agency whose technicians join remote sessions, the key check is simple: every technician client must be on version 26.6.5 or later, not just the server.
What happened
ConnectWise fixed CVE-2026-84869 on September 8, 2026. The bulletin describes a condition in the ScreenConnect client that may allow files to be transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances.
Since then, researchers have described several waves of activity. SecurityWeek, citing Huntress, reports that exploitation started on August 20, before the patch, and that since October 20 Huntress has seen at least 688,000 guest "run file" requests for update*.bat hit 42 MSP ScreenConnect servers from 29 IP addresses. Huntress describes this as blind spraying that waits for any technician to join a session.
Blackpoint Cyber's Adversary Pursuit Group separately analyzed SCKit. It confirmed that the toolkit's exploit targets CVE-2026-84869 and that a fully patched client blocks the payload. Huntress says the activity it saw differs from the SCKit and fake crypto exchange campaigns, so these are described as separate clusters.
How SCKit works
The weakness class is missing authorization: a session participant on the guest side can push a file and have the technician's client run it, without the technician confirming. The technician sees no prompt when it executes, according to Huntress.
According to Blackpoint's findings as reported by The Hacker News, SCKit works in stages:
- It uses ScreenConnect's built-in Run Command feature on an already reachable endpoint to install attacker-controlled ScreenConnect Access clients for persistent control.
- A component called RelayTrap interferes with ScreenConnect Guest sessions. When a technician connects to investigate, it tries to send a payload back to the technician using the guest-to-host execution technique tied to CVE-2026-84869.
- If that works, the malware looks for the technician's authenticated ScreenConnect browser sessions (.ASPXAUTH cookies) and reuses them to push commands to other endpoints that technician can manage.
Blackpoint warns that this last step does not depend on a software flaw once the attacker holds a valid session. In its words as quoted by The Hacker News, patching addresses the known exploit but does not eliminate the risks associated with a compromised operator session.
Who is exposed
Anyone using the ScreenConnect client for remote support is in scope, but MSPs carry the most risk. An MSP technician workstation typically holds RMM consoles, saved credentials and access to many customers, which is why Huntress calls it an especially attractive target. One compromised workstation can become a route into every customer that technician serves.
Cloud-hosted ScreenConnect needs no server action per ConnectWise, but after the upgrade you must reinstall host clients and update access agents. On-premises operators must upgrade the server themselves and also verify clients. Updating the server alone does not confirm that technician clients are updated.
How to check your exposure
- List every workstation where technicians run the ScreenConnect host client and record the installed client version. Per ConnectWise, versions prior to 26.6.5 are affected, and 26.6.5 or later is the required level.
- Check the ScreenConnect access agents ConnectWise lists in its bulletin and confirm they are updated as well.
- On on-premises servers, check whether any of these extensions are installed: Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link, RMM+ Password Link. ConnectWise also disabled ITBoost Integration, RepairShopr Integration and Guest Session Starter in cloud environments and its marketplace as a precaution, and encourages partners to do the same.
- Review Run Command history, extension API activity, administrative accounts, permission changes and Toolbox records for commands you do not recognize, as ConnectWise advises. Also look for unapproved remote-access software, such as extra ScreenConnect Access clients, which is what Blackpoint describes SCKit installing.
- Optionally, compare against indicators Huntress observed in its separate spraying campaign: guest "run file" requests for update*.bat, a rogue ScreenConnect client disguised as Windows Update, and, in one targeted attack, a script dropped into a technician's Startup folder. These are indicators from that campaign only; the sources do not say where in ScreenConnect or your logs to look for them, so absence of these is not proof of safety.
What to do now
- Update ScreenConnect to 26.6.5 or later. On-premises partners download it from the ScreenConnect download page (a valid on-premises license is required, and out-of-maintenance licenses must be upgraded first).
- After upgrading, reinstall host clients and update access agents, then verify the version on every technician workstation individually.
- If you cannot update immediately, as a temporary mitigation only: go to Administration > Security > Roles, edit each role, review each session group with permissions, deselect TransferFiles, and save. Repeat for every role. This does not replace the update.
- On-premises: disable the five identified third-party extensions now, and do not re-enable or reinstall them pending ConnectWise guidance. ConnectWise cannot do this for on-premises installs.
- From a trusted device, revoke active ScreenConnect and identity-provider sessions, reset relevant credentials and enforce MFA. ConnectWise notes password resets alone do not invalidate all existing sessions.
- Review audit logs, users with access, and permission changes. Look for unapproved remote-access tools.
- If you suspect compromise, follow incident response: isolate affected servers, keep backups for analysis, and do not bring them back until they are investigated, rebuilt and patched. A compromised ScreenConnect server may not be the only entry point.
Detection and ongoing monitoring
Because SCKit abuses legitimate features, signature-only detection will miss parts of it. Based on what the researchers and ConnectWise describe, watch for: unauthorized or extra ScreenConnect Access clients, unexpected Run Command history, files pushed from guest to host without a technician prompt, and unexpected items in a technician's Startup folder (seen in one Huntress case). As general advice rather than reported behavior, keep a current inventory of approved remote-access tools so extras stand out.
If your own public sites sit behind the same administrators, review who can reach them and rotate credentials those technicians held. Certificate, DNS and header-change monitoring can help you notice unexpected changes to your public sites, and our guide on what to do when a website is hacked covers the response steps. None of this replaces patching the ScreenConnect clients themselves.
Timeline
| Date | Event |
|---|---|
| August 20, 2026 | Exploitation started, per Huntress as reported by SecurityWeek |
| September 8, 2026 | ConnectWise releases ScreenConnect 26.6.5 and publishes the bulletin; CVE published |
| September 11, 2026 | CISA adds the CVE to its KEV catalog, per SecurityWeek |
| October 20, 2026 | Huntress-observed spraying campaign against MSP servers begins |
| November 12, 2026 | Blackpoint details SCKit and RelayTrap |
| November 13 and 16, 2026 | ConnectWise advisory updates: disable extensions, verify technician clients on 26.6.5 or later; investigation complete but action still required |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
