ConnectWise is investigating unauthorized access to customer environments after a wave of intrusions was linked to a third-party extension for its ScreenConnect remote management tool. The extension, RMM+, lets outside management tools automate remote sessions through an API.

Huntress said it saw 288 affected endpoints across 48 organisations, all targeted within 90 minutes. The security firm found commands tied to RMM+. ConnectWise said roughly 400 partner environments have at least one independently developed extension from the RMM+ family installed, but stressed that having the extension installed does not prove a system was compromised.

The company has disabled RMM+ and four other third-party extensions while it investigates. For managed service providers (MSPs), the businesses that run IT for other companies, the incident is a reminder that the tools they use to manage everyone else’s systems are themselves a high-value target.

What is RMM+?

ScreenConnect, formerly ConnectWise Control, is remote-support software. MSPs use it to connect to clients’ computers, run updates, troubleshoot problems and manage devices without visiting an office. It is part of a category called remote monitoring and management (RMM), which sits at the centre of most managed-service operations.

RMM+ is an extension built by a third party. It adds a way for other management platforms to start and control ScreenConnect sessions through an API, which is a set of rules that lets one program ask another to do something. The convenience is obvious: a technician can trigger a session from a dashboard instead of opening a second tool.

The risk is that extensions run with the same level of trust as the core server. If an extension has a flaw, or if an attacker can abuse its integration, the attacker may inherit the access of the management platform. That is why the extension layer matters as much as the ScreenConnect server itself.

What is CVE-2026-84869?

The attacks have been tied to CVE-2026-84869, a critical flaw in ScreenConnect that was patched in September. CVE is a public catalogue number for a security vulnerability; the number makes it easier for vendors and defenders to track the same issue.

The flaw was added to CISA’s Known Exploited Vulnerabilities list on 11 September. That list is the US government’s catalogue of bugs that attackers are known to use in the wild, and inclusion is a signal to patch immediately rather than schedule the work for later.

Blackpoint Cyber told Recorded Future News that the attackers’ toolkit exploits the flaw. Testing against a fully patched client blocked the payload, Blackpoint said, but the investigation is still early. Patching is necessary. It is not the whole response.

How the campaign unfolded

The numbers are small per customer and large in aggregate. 288 endpoints across 48 organisations is about six endpoints per organisation, all within 90 minutes. That pattern is consistent with automated scanning for exposed ScreenConnect instances followed by hands-on activity, rather than a campaign aimed at one industry or one large target.

That distinction matters for defenders. A broad, automated campaign can hit many MSPs at once, and each MSP may serve dozens or hundreds of downstream businesses. The blast radius is not the number of initial victims. It is the number of customers those victims can reach.

What MSPs should do now

ConnectWise has disabled five extensions, but partners should not assume that is the end of the cleanup. The immediate checklist is concrete:

  • Inventory every installed extension and disable anything not actively used. ConnectWise has already disabled five; confirm what remains.
  • Rotate API keys, integration credentials and any service accounts that can reach ScreenConnect.
  • Review ScreenConnect audit logs for new local administrators, unexpected session launches and commands run outside normal hours.
  • Verify the CVE-2026-84869 patch level on every instance, including relays and self-hosted servers. A relay is the server that helps connect technicians to remote devices; an unpatched relay can undo a patched console.
  • Segment RMM servers from flat networks and enforce multi-factor authentication on technician accounts. MFA asks for a second proof of identity, such as a code from a phone.
  • Check endpoint telemetry for signs of lateral movement, and isolate any host that shows unexpected remote sessions.
  • Notify affected customers according to your contracts, even if the vendor has not named them.

The disclosure burden is the other immediate issue. ConnectWise has confirmed the investigation but not which customers were affected, and MSPs may learn about intrusions from their own endpoint logs first. Waiting for a vendor notification is not a plan.

The contractual side matters too. MSPs often have obligations to tell their clients about security incidents within a set window. Legal counsel should be involved early, and the notification should say what is known, what is not known and what customers should do. Vague reassurance is worse than a clear timeline.

What to watch

Three things. First, whether the campaign spreads to technician workstations, which would give attackers a foothold inside the providers themselves. Second, whether the patch is genuinely sufficient; Blackpoint’s test is encouraging, but one test is not a guarantee. Third, whether ConnectWise restores the disabled extensions and what security requirements it attaches to them.

The broader question is whether the RMM extension ecosystem can be trusted by default. Extensions are useful because they let partners customize their tools. They are dangerous for the same reason.

The bigger lesson

ScreenConnect is not the first management tool to become an attack path. Kaseya’s VSA incident in 2021 showed how compromising the management layer can reach hundreds of downstream businesses through their providers. The pattern repeats because the economics are attractive: one successful intrusion can unlock many customers.

For MSPs, the lesson is to treat remote-management software as tier-zero infrastructure, the kind that deserves the strongest controls, the most logging and the fastest patching. That means knowing every extension, every integration and every account that can reach the server. It also means assuming that a vendor’s security advisory is the start of the work, not the end.

The bottom line

The ConnectWise ScreenConnect attacks are a supply-chain problem in miniature. The core product was patched. The extension layer became the way in. MSPs that inventory, isolate and monitor that layer will be harder to reach. Those that wait for a vendor notification may find out from their own logs first.

Have a tip? Email [email protected] or use the contact form and choose Editorial. We do not promise anonymity.

Source: The Record; The Hacker News.