Rogue ScreenConnect clients hit 288 endpoints across 48 organizations
Attackers used access to cloud-hosted ScreenConnect panels to push rogue clients to at least 288 endpoints in 48 organizations. Huntress and ConnectWise found no new vulnerability behind the November campaign.
What happened
According to The Hacker News, Huntress observed rogue ScreenConnect clients on at least 288 managed endpoints across 48 organizations. The report said the activity was first detected on November 11, 2026, at around 5:47 p.m. UTC. According to the report, attackers used a compromised ScreenConnect panel’s Run Command feature to deploy rogue clients, and telemetry pointed to compromised credentials or hijacked operator sessions for initial access. The report also said Huntress had not seen evidence of a new vulnerability in the attacks. ConnectWise said it has found no evidence of a compromise of its infrastructure or a vulnerability in ScreenConnect itself.
Why it matters
ConnectWise disabled five third-party ScreenConnect extensions across approximately 400 partner environments as a precaution. It advised on-premises partners to disable those extensions themselves and not to re-enable or reinstall them pending further guidance. ConnectWise warned that disabling extensions and resetting credentials alone may not remove unauthorized software, persistence mechanisms, or access already established on endpoints.
What to do
Revoke active ScreenConnect and associated identity-provider sessions, reset relevant passwords, and verify that multifactor authentication is enforced. Avoid interactive ScreenConnect sessions to suspected compromised devices and use separate security tooling. Preserve authentication, extension installation, administrative, Run Command, and Toolbox records.
Separately, on-premises servers should already run ScreenConnect 26.6.5 or later. That release, from the September 8, 2026 bulletin, fixes CVE-2026-84869, an older flaw (CVSS 9.9) that CISA added to the Known Exploited Vulnerabilities catalog on September 11, 2026. No source links it to the November campaign.
Sources
Story timeline
-
Corrected the framing: the November rogue-client campaign is not CVE-2026-84869. Huntress and ConnectWise found no new vulnerability; the CVE was patched on September 8, 2026 and is now noted as separate patch hygiene.
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .