ConnectWise traces ScreenConnect breaches to RMM+ extension
A remote-management add-on with command execution is not a side issue when technician sessions can become the attacker’s bridge.
TL;DR
Recorded Future News reports ConnectWise is investigating unauthorized access tied to the RMM+ extension for ScreenConnect, after Huntress saw 288 affected endpoints across 48 organizations. ConnectWise found about 400 partner environments with an RMM+ family extension installed, disabled it where it could, and told on-premises customers to do the same. Presence alone doesn’t prove compromise, which is exactly why endpoint review still matters.
Recorded Future News reports that ConnectWise has traced the latest ScreenConnect customer-access reports to RMM+, an independently developed third-party extension that lets external management tools automate and control remote sessions through an API. ConnectWise said it found about 400 partner environments with at least one extension from the RMM+ family installed, while stressing that installation alone doesn’t establish compromise.
That caveat matters, but it doesn’t make the operational problem small. ConnectWise told customers the activity included deployment of additional remote-access software and possible compromise of technician workstations during interactive connections to affected devices. Huntress, whose findings helped trigger the response, said it saw 288 affected endpoints across 48 organizations within 90 minutes and has not seen evidence of a new vulnerability, according to The Record.
ConnectWise said it disabled RMM+ in the environments it could reach and told customers with on-premises systems to disable it themselves because the company can’t do that for them. It also told customers to verify RMM+ is disabled and warned that disabling extensions or resetting credentials may not remove unauthorized software, persistence, or access already established on endpoints.
For managed service providers and customers that use ScreenConnect as privileged plumbing, that is the real Monday work. This isn’t only a settings check in an admin console. If ScreenConnect touched endpoints during the window in question, the useful question is whether access already moved beyond the extension into remote-access tools, persistence mechanisms, or technician workstations. The product boundary is neat. The incident boundary usually isn’t.
Published ·Deep Fathom