ConnectWise disables ScreenConnect extensions amid investigation
ConnectWise is investigating reports that a threat actor is abusing third-party extensions in ScreenConnect environments to run malicious commands and maintain remote access. As a precaution, the company has disabled access to several RMM+ extensions in about 400 environments and advised on-premises partners to disable their own third-party extensions.
The activity has raised concern among managed service providers and the organizations they support because ScreenConnect is used for remote administration. ConnectWise said its initial assessment suggests independent third-party extensions installed in partner environments may be involved, but it has not confirmed how the actor gained initial access. The company said it cannot disable extensions unilaterally in on-premises partner environments.
Researchers report unauthorized clients and a malware toolkit
Huntress reported finding rogue ScreenConnect clients on at least 288 managed endpoints across 48 organizations. According to the firm, those clients install a toolkit called SCKit. Huntress described the activity as an effort to establish persistent remote access and deploy malware that could potentially steal session cookies.
Huntress researchers said the attacker uses ScreenConnect’s Run command to deploy SCKit. The toolkit comprises 16 files, including PowerShell scripts, batch scripts and Windows command-line files. The files support a multistage infection process, the researchers said. These details indicate that defenders should examine both remote-management activity and the subsequent execution of scripts or other tools on managed systems.
Sophos researchers are also investigating similar activity involving unauthorized ScreenConnect deployments. BlackPoint researchers have described a Relay/Trap component intended to affect technicians who attempt to connect to an impacted machine. BlackPoint associated the reported “guest-to-host” behavior with CVE-2026-84869, a previously disclosed vulnerability that the Cybersecurity and Infrastructure Security Agency added to its Known Exploited Vulnerabilities catalog in September.
Researchers have not established whether CVE-2026-84869 was successfully exploited in this campaign. The reported connection to the vulnerability should therefore be treated as an investigative lead, not confirmation of the attackers’ initial access method or a proven explanation for every affected deployment.
Containment and investigation priorities
ConnectWise identified the disabled extensions as Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link and RMM + Password Link. Partners should verify that third-party extensions are disabled in their environments, including where the company cannot make that change for them.
For organizations investigating a suspected incident, ConnectWise recommends using separate tooling rather than interactive ScreenConnect sessions. This helps avoid relying on a potentially affected remote-access channel while examining systems. Administrators should secure administrative access from a trusted device, revoke active ScreenConnect sessions and passwords, and use multifactor authentication.
Evidence preservation is also important. ConnectWise specifically advised partners to retain authentication records, extension installation records, Run command records and Toolbox records. Security teams can use these records to establish timelines and identify suspicious administrative or deployment activity. Correlating those records with endpoint investigation findings may help determine whether unauthorized clients or SCKit components are present, while preserving evidence for further analysis.
Because the entry point remains unconfirmed, organizations should avoid assuming that disabling extensions alone resolves a suspected compromise. The reported activity spans remote-access deployment, command execution and toolkit installation, so investigation should cover the relevant endpoints and administrative activity as well as extension settings. Partners should follow ConnectWise’s containment guidance and assess their own environments using trusted tools.
The incident also illustrates the operational risk of third-party components within remote-management platforms: an extension can create an additional path that defenders need to account for during both routine monitoring and incident response. ConnectWise’s temporary action affects about 400 environments, while on-premises partners must take their own steps. The available reporting does not establish the campaign’s full scope, its initial access method or whether the cited vulnerability was used.