November 17 update: investigation closed, protective actions still required
ConnectWise’s November 16 update, posted at 20:00 UTC, says its investigation is complete but reports continued targeting of unremediated on-premises installations. The company instructs operators to keep Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link and RMM+ Password Link disabled and update their servers to a supported release.
All partners must separately verify every technician client runs 26.6.5 or later, which includes the September fix for CVE-2026-84869. Updating a server does not establish that its technician workstations were updated.
The vendor emphasizes that closing its investigation does not certify customers as unaffected. Disabling extensions and patching do not remove unauthorized persistence already established. Review sessions and activity, and investigate suspected compromise with separate security tools. Read the current ConnectWise advisory.
This dated update supersedes the investigation-status wording in the original November 16 report, preserved below as the earlier record.
ORIGINAL IPCRIME REPORT | NOVEMBER 16, 2026
An active campaign against ConnectWise ScreenConnect partner environments remains a serious managed-service-provider risk. Huntress reported an initial November 11 wave affecting at least 288 managed endpoints at 48 organizations, followed by 205 additional hosts at 41 organizations in activity observed November 13. ConnectWise’s November 13 guidance told partners to disable specified third-party extensions and verify that technician clients were patched.
What researchers observed
Huntress says attackers ran commands via compromised ScreenConnect panels to install attacker-controlled ScreenConnect clients and a toolkit it calls SCKit. The toolkit can establish unauthorized remote access and relay session cookies. The researcher’s counts describe endpoints and organizations it observed, not a definitive world-wide total; the two waves also should not automatically be added into a count of unique organizations without checking for overlap.
ConnectWise’s earlier assessment
ConnectWise said it identified approximately 400 partner environments with one or more third-party RMM+ family extensions. The mere presence of an extension does not mean an environment was compromised. The company said it had not found evidence of a compromise of its own infrastructure or that initial access involved a vulnerability in ScreenConnect itself. At the time of the initial report, full scope and initial entry routes remained under investigation.
Initial defensive guidance
ConnectWise instructed on-premises partners to disable the named extensions and all partners to ensure technician clients run ScreenConnect 26.6.5 or later, while checking the latest vendor advisory for subsequent releases. Changing passwords does not necessarily invalidate existing sessions. Teams should use independent endpoint-detection or other trusted out-of-band tools to investigate systems already suspected of compromise rather than relying on a potentially abused ScreenConnect session.
Why MSP incidents have a wider footprint
Remote-management systems intentionally allow technicians to reach many customer endpoints. A compromised console, overly permissive extension or session token can multiply a single trust failure. Containment therefore involves management consoles, extension configurations, issued sessions, customer endpoints and potentially persistent remote clients.
Source documents and reporting
- Huntress SCKit investigation, updated November 13
- ConnectWise Trust Center advisories, including November 16 update
- BleepingComputer initial coverage, November 11
IPCRIME identifies confirmed company or agency disclosures separately from outside reporting and attacker claims. Originally published November 16, 2026; updated November 17 without changing the original publication date.