Update: This follows my post on ScreenConnect attacks that used an already-patched bug and then hijacked sessions. ConnectWise said Monday it has completed its investigation into unauthorized access targeting partner ScreenConnect environments, The Hacker News reports, and it wants customers to make sure the technician client is on version 26.6.5 or later. That release addresses CVE-2026-84869, the already-patched flaw I wrote about earlier. The company says additional activity is still being reported against on-premises environments where the identified third-party extensions remain enabled and ScreenConnect has not been updated.
On-prem partners must disable those extensions and update to the latest supported version. ConnectWise had already disabled five third-party extensions across about 400 partner environments and is telling partners not to turn them back on until further guidance. Huntress reported another spike in related activity on November 13, affecting 205 hosts across 41 organizations. ConnectWise also warned that disabling extensions and updating software does not remove unauthorized access or persistence already established on affected devices. Check for unexpected access, and hang on to your logs.
Review before you install: read the release notes yourself, back up your config, and try new versions somewhere you can afford to break first.
My take
Closing the investigation is not the same thing as the campaign being over. If you run ScreenConnect, get the technician client to 26.6.5 or later, leave the flagged extensions off, and look for anything that may already have been left behind. A patch will not clean up a session that was stolen last week.
God Bless, and May the Source Be with You!