What Happened
ConnectWise said on Monday that it completed its investigation into unauthorized access that targeted partner ScreenConnect environments. Hackernews reports that the company recommended customers ensure the technician client is running version 26.6.5 or later. That is the primary action from the source on these ConnectWise ScreenConnect attacks.
The company also said additional activity targeting on-premises environments continues to be reported where the identified third-party extensions remain enabled. It said SCKit is going after unpatched systems.
For an MSP, this is a remote access tool that sits inside client environments. Unauthorized access to a remote access tool is not a single-client problem. It can give an attacker a path into every environment that tool reaches. That is why the vendor's version check and on-premises extension review matter to the whole book of business.
Timeline
- Monday: ConnectWise said it completed its investigation into unauthorized access targeting partner ScreenConnect environments and recommended customers ensure the technician client is running version 26.6.5 or later.
- November 17, 2026: Hackernews published its report on the ConnectWise statement.
Who Is Affected
The source lists ConnectWise ScreenConnect partner environments, on-premises ScreenConnect environments with third-party extensions enabled, and the ScreenConnect technician client. If you run ScreenConnect as an MSP, your environments and your clients' environments are in scope.
On-premises deployments with third-party extensions enabled are called out specifically because additional activity continues where those extensions remain enabled. The technician client version matters for every technician who connects. If one technician workstation is behind, that is a potential entry point into the environments that technician can reach.
Why This Class of Attack Matters to MSPs
Remote access tools are built to cross boundaries. That is the point: a technician uses one tool to reach many client networks. When an attacker gets unauthorized access to that tool, the blast radius is not one endpoint. It is every environment the tool can reach, and the trust your clients place in you to keep those environments separate and controlled.
As a standing practice, remote access tools deserve the same hardening you apply to other privileged access: strong authentication, least privilege, logging, and a short window between a vendor patch and deployment. The cost of a missed version check is not just the licence or the support call. It is the hours of containment, the client conversations, and the recovery work that follows an intrusion.
The source does not describe how many MSPs or clients are affected. It does describe ongoing activity, which means this is not a one-day patch event. Treat it as a verification task you repeat until you can show every technician client and every on-premises extension is accounted for.
Technical Details
CVE: The source does not list a CVE for this activity. Product: ConnectWise ScreenConnect. Versions: The technician client must be running version 26.6.5 or later. Attack vector: unauthorized access targeting partner ScreenConnect environments. Additional activity targeting on-premises environments continues to be reported where the identified third-party extensions remain enabled. SCKit is going after unpatched systems.
Those are the details the source provides. Nothing else about the incident is confirmed in the source.
What MSPs Should Do About ConnectWise ScreenConnect Attacks
Start with the vendor's own guidance, then close the gaps that let an attacker keep a foothold in a remote access tool. Work through this list in order and record what you change.
- Ensure the ScreenConnect technician client is running version 26.6.5 or later.
- If you run on-premises ScreenConnect, review every third-party extension. ConnectWise says additional activity continues where the identified third-party extensions remain enabled. Disable or remove any extension you do not need.
- Patch unpatched systems. The source says SCKit is going after unpatched systems.
- Check remote access logs for unfamiliar sessions, new accounts, or changes you did not make.
- Reset credentials for any account that may have been exposed. Enable MFA on remote access tools as a standing practice.
- Confirm you have clean, isolated backups for client environments and that you can restore them.
- Tell clients what you found and what you changed, following your normal client communication process.
How EnterProtect Helps
EnterProtect backup keeps clean, restorable copies of client systems and data. If an attacker gets into a remote access tool and damages or encrypts a client environment, the backup is what lets you restore that client to a known good state.
EnterProtect recovery gets a client running again. When a remote access tool is the entry point, the recovery process is about rebuilding the client environment from clean copies, not just replacing files. That is the work that stops one incident from becoming a lost client.
As a standing practice, EnterProtect vulnerability scanning helps MSPs find exposed versions across client environments so they can prioritise patching. EnterProtect does not detect, block or prevent the activity ConnectWise described. It is the recovery and visibility layer you need when prevention fails.
Frequently Asked Questions
What Is the ConnectWise ScreenConnect Attack?
ConnectWise said it completed an investigation into unauthorized access that targeted partner ScreenConnect environments. The company also said additional activity targeting on-premises environments continues where identified third-party extensions remain enabled. Hackernews reports that SCKit is going after unpatched systems.
Which ScreenConnect Version Should MSPs Be Running?
ConnectWise recommended that customers ensure the technician client is running version 26.6.5 or later. That is the version the source names. Check every technician workstation, not just the server.
What Should MSPs Do First After This ScreenConnect Warning?
Start by checking the technician client version and confirming it is 26.6.5 or later. Then review on-premises ScreenConnect deployments for third-party extensions that are enabled. Patch unpatched systems and review remote access logs for unusual activity.
Is There a CVE for This ConnectWise ScreenConnect Activity?
The source does not list a CVE for this activity. There is no CVE identifier in the report. Treat the vendor's version guidance and the on-premises extension review as the confirmed actions.
What Is SCKit?
The source says SCKit is going after unpatched systems. That is the only description the source gives. The name is used in the ConnectWise statement as reported by Hackernews.
Do On-Premises ScreenConnect Environments Need Different Handling?
ConnectWise said additional activity targeting on-premises environments continues to be reported where the identified third-party extensions remain enabled. If you run on-premises ScreenConnect, review every third-party extension. Disable or remove any extension you do not need.
Sources
- ConnectWise Warns ScreenConnect Attacks Continue as SCKit Targets Unpatched Systems (Hackernews)