ConnectWise Wraps Up Investigation, But the Attacks Haven't Stopped
ConnectWise has closed the book on its internal investigation into unauthorized access affecting partner ScreenConnect environments, but the company's message to customers is anything but a clean bill of health. In an update published Monday, the remote monitoring and management (RMM) vendor said it has completed its review of the intrusion and is now pointing administrators toward a specific remediation baseline: the ScreenConnect technician client must be running version 26.6.5 or later.
More troubling is what ConnectWise says is still happening in the wild. The company reported that additional activity against on-premises deployments continues to be observed, specifically in environments where the third-party extensions identified during the investigation remain enabled. In other words, closing the investigation does not mean the threat has been neutralized for customers who haven't acted on the guidance.
What Happened
The incident centers on ScreenConnect, ConnectWise's widely deployed remote access and support tool. Because ScreenConnect is used by managed service providers (MSPs) and IT teams to reach customer endpoints at scale, a compromise of the platform carries outsized risk: attackers who gain a foothold in a ScreenConnect instance can inherit the trust relationships that technicians already enjoy across client networks.
ConnectWise's investigation examined unauthorized access targeting partner environments. The company's remediation advice narrows to two practical steps: upgrade the technician client to 26.6.5 or newer, and disable the third-party extensions flagged during the probe in any on-premises installation where they are still active. The vendor's language suggests that leaving those extensions in place is the common thread connecting the ongoing reports of malicious activity.
Why On-Premises Installations Bear the Brunt
Cloud-hosted ScreenConnect instances are patched and managed by the vendor, but on-premises servers put the upgrade and configuration burden squarely on the customer. That split is a recurring theme in RMM security incidents: self-hosted deployments lag behind on updates, extensions accumulate over time, and the resulting attack surface is both broad and difficult to inventory.
For MSPs, the stakes are compounded. A single unpatched ScreenConnect server can expose every customer tenant that routes through it, turning one neglected administrative tool into a lateral-movement highway. The continuing reports of activity against on-premises systems are a signal that a meaningful population of instances has not yet applied the fix or removed the implicated extensions.
The SCKit Angle
Coverage of the campaign has tied the activity to tooling tracked as SCKit, which targets unpatched ScreenConnect systems. The naming reflects a familiar pattern in RMM abuse: purpose-built offensive utilities that automate discovery and exploitation of exposed management infrastructure. Because ScreenConnect is legitimately installed in many networks, malicious use of the platform can blend into normal administrative traffic — a characteristic that has made RMM tools attractive to both ransomware affiliates and state-linked operators in recent years.
ConnectWise has not, in its public statement, attributed the activity to a specific threat actor, and details about the full scope of the original unauthorized access remain limited. What the vendor has made clear is the operational priority: version 26.6.5 as a floor, and no lingering third-party extensions on premises.
Recommended Actions for Administrators
- Verify your build. Confirm the ScreenConnect technician client is on version 26.6.5 or later. Check both server and client components, and audit any instances managed on behalf of clients.
- Audit extensions. Inventory all third-party extensions on on-premises servers and disable anything identified in ConnectWise's guidance as implicated in the investigation.
- Restrict exposure. ScreenConnect instances should never be reachable from the open internet without compensating controls. Review firewall rules, VPN requirements, and MFA enforcement on technician accounts.
- Hunt for anomalies. Review logs for unusual session creation, unexpected technician account activity, and outbound connections originating from the ScreenConnect host.
- Inventory shadow deployments. MSPs frequently discover forgotten trial or departmental installs. Sweep your estate for ScreenConnect instances that fall outside central management.
The Bigger Picture
This episode reinforces a lesson the security community has learned repeatedly: management tooling is high-value terrain. Products built to grant trusted, privileged access are precisely what adversaries want to co-opt, and vendors' investigations closing is not the same as customer risk closing. ConnectWise's disclosure puts the onus on administrators to confirm their own posture — and the continued reports of exploitation suggest many have yet to do so.
Organizations running ScreenConnect on-premises should treat this as an active, unresolved exposure rather than a post-incident cleanup. Patch, prune extensions, and verify that nothing is listening on the public internet that shouldn't be.