
ConnectWise alerts about ongoing attacks and SCKit malware in ScreenConnect
ConnectWise concluded investigation into incidents in ScreenConnect, recommending immediate update and disabling vulnerable third‑party extensions.
ConnectWise has concluded its investigation into the unauthorized access incidents targeting partner environments using ScreenConnect. The company issued an alert emphasizing the urgent need for all customers to ensure that the technical client is running version 26.6.5 or later, designed to mitigate active exploitation vectors.
According to the official statement, malicious activity continues to be reported in on-premises environments where identified third-party extensions remain enabled and the software has not been updated. Recent attack campaigns have taken advantage of plugin flaws and known vulnerabilities to automate the distribution of malicious toolkit packages into Managed Service Provider (MSP) corporate environments.
The Exploitation of Extensions and the SCKit Mechanism
Security researchers from Huntress, Blackpoint Cyber, and Microsoft detailed that attackers are exploiting authentication flaws in specific versions of extensions within the RMM+ ecosystem, such as Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link, and RMM+ Password Link. These extensions expose programming interfaces and functionalities that allowed remote command execution without proper authentication.
The attacks deploy a multi-component toolkit named SCKit, composed of various scripts and C# modules. Among the modules, RelayTrap stands out, designed with lateral propagation capability and "worm" behavior. The main objective of this vector is to target IT technicians' workstations the moment they perform remote support on an already compromised client device, injecting files and executing arbitrary commands in the operator's environment.
Associated Vulnerability and Manufacturer Actions
The critical vulnerability CVE-2026-84869, with a CVSS score of 9.9 and listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, plays a central role in the incidents. It allows the transfer and execution of files in active remote sessions without Host confirmation. While initial reports indicated no success in lateral propagation to technicians, subsequent analysis by Huntress confirmed active in-the-wild exploitation of this flaw in mid-November 2026, with dozens of organizations impacted.
As a containment measure, ConnectWise proactively disabled five third-party extensions in approximately 400 affected partner environments. The corporation emphasizes that simply disabling extensions and applying patches does not remove previously established unauthorized access or persistence, requiring thorough auditing and incident response on exposed endpoints.
CyberX Technical Analysis
The analysis of the incident architecture evidences a hybrid vector combining logical flaws in third-party extensions with native code execution vulnerabilities on the ScreenConnect client. The exploitation leverages the inherent trust in remote support sessions established between MSP operators and managed endpoints.
Surface Vector and Modus Operandi
- Extension Flaws: Extensions in the RMM+ family exhibited access control deficiencies and static API secrets, allowing external agents to issue commands without strict validation.
- "Guest-to-Host" Dynamics: SCKit uses the RelayTrap module to wait for incoming connections from support technicians. Upon detecting the active session, it injects batch scripts (such as .bat files) and utilities to download the malicious ScreenConnect client and establish persistence via scheduled tasks and registry keys.
- Persistence and Evasion: In some analyzed incidents, the creation of fake services mimicking legitimate operating system components was observed, such as services tied to Windows Update in protected ProgramData directories.
Mitigation and Defensive Verification
Organizations using ScreenConnect must immediately audit the version of their technician clients (ensuring version 26.6.5+) and check for anomalous processes originating from remote control sessions. Thorough review of access logs, inspection of newly created executable files in temporary directories, and validation that problematic extensions remain disabled are strongly recommended.
CyberX SOC Intelligence Bulletin
SOC operators and incident response teams must actively monitor remote management infrastructure for suspicious executions originating from ScreenConnect processes, focusing on identifying scripts executed by guest sessions and the integrity of technical support team workstations.
Operational Indicators and Hunting Vectors
- Processes and Executables: Monitor the creation of unexpected batch scripts (.bat, .ps1) originating from ScreenConnect execution contexts, as well as files associated with the SCKit package in system directories.
- Services and Persistence: Investigate new registry entries (Run/RunOnce) and newly created services with generic names or mimicking Windows components (e.g., fake update agent).
- Network Connections: Analyze unusual outbound traffic originating from technician endpoints toward unknown infrastructure hosts or bulletproof hosting.
Practical Mitigation
Apply the corrective patch for CVE-2026-84869 by updating to version 26.6.5 or higher and keep the RMM+ line extensions listed by ConnectWise disabled. Adopting robust multi-factor authentication and restricting privileges for administrative access to management servers are fundamental barriers to containing lateral movement.
Frequently asked questions
What is the recommended version of ScreenConnect to mitigate the attacks?
ConnectWise recommends ensuring the technical client is running version 26.6.5 or later.
What is SCKit?
SCKit is a multi-component malware toolkit composed of scripts and C# modules, including RelayTrap, designed for lateral propagation and targeting IT technicians' workstations.
Which critical vulnerability plays a central role in these incidents?
The critical vulnerability CVE-2026-84869, which has a CVSS score of 9.9 and is listed in CISA's Known Exploited Vulnerabilities catalog.
Are disabling extensions and patching enough to secure an environment?
No, simply disabling extensions and applying patches does not remove previously established unauthorized access or persistence, so a thorough audit and incident response are required.


