ScreenConnect Attacks Hit 288 Endpoints via Rogue Clients

Introduction
ConnectWise has taken the precautionary measure of disabling five third-party extensions within its ScreenConnect remote access platform after detecting unauthorized access activity spanning at least 288 endpoints across 48 distinct organizations. The company posted an advisory stating that its initial investigation found no evidence of a compromise to ConnectWise infrastructure itself, nor any vulnerability in the core ScreenConnect software. Instead, the activity appears to center on the extension ecosystem and the deployment of unauthorized, rogue client instances.
Scope and Immediate Response
According to the advisory, the malicious activity was identified through reports of unauthorized access. ConnectWise responded by disabling the five implicated third-party extensions across partner environments to contain further exposure. The scale—288 endpoints in 48 organizations—suggests a coordinated campaign rather than isolated intrusion attempts. Because the core platform and vendor infrastructure remain uncompromised, the incident highlights the risk posed by the broader software supply chain, specifically the trust placed in third-party add-ons that extend remote management capabilities.
Technical Context: Rogue Clients and Extension Abuse
Remote monitoring and management (RMM) tools like ScreenConnect are high-value targets because they provide legitimate administrative access to managed endpoints. Threat actors increasingly abuse these tools by registering rogue clients—unauthorized agents that masquerade as legitimate managed devices—or by weaponizing extensions that run with elevated privileges. In this case, the malicious extensions likely served as a persistence or lateral movement mechanism, allowing attackers to blend in with normal administrative traffic. The fact that ConnectWise could isolate the issue to specific extensions without implicating the base product underscores the importance of extension vetting, signing enforcement, and runtime monitoring.
Impact on Managed Service Providers and Enterprises
Organizations that rely on ScreenConnect—whether directly or through managed service providers (MSPs)—should treat this as a potential supply chain event. Even if their own tenants were not among the 48 confirmed victims, the disabled extensions may have been installed in other environments. MSPs must audit every extension deployed across customer tenants, verify publisher authenticity, and review extension permissions. Endpoint detection and response (EDR) telemetry should be correlated with ScreenConnect logs to identify any rogue client registrations or anomalous session activity that predates the advisory.
Practical Mitigation Steps for Defenders
- Inventory all ScreenConnect extensions in every tenant; remove or disable any not explicitly approved.
- Enforce extension signing and publisher verification policies; block unsigned or unverified add-ons.
- Monitor for rogue client registration by alerting on new agent enrollments that lack change-management tickets.
- Review session logs for connections originating from unusual geographies, at odd hours, or using service accounts not tied to known administrators.
- Apply least-privilege principles to extension permissions; restrict network access, script execution, and file transfer capabilities to the minimum required.
- Engage with ConnectWise support for the latest indicator-of-compromise (IOC) feed and guidance on re-enabling extensions safely.
Grivyonx Expert Analysis
This incident reinforces a pattern we track closely: attackers targeting the extensibility layer of widely deployed RMM platforms rather than the core codebase. Extensions often run with SYSTEM or root privileges and inherit the trust of the parent agent, making them ideal stealth footholds. Defenders should treat every third-party extension as a potential supply chain vector—subjecting them to the same rigorous code review, behavioral baselining, and continuous monitoring applied to the primary agent. Automation that correlates extension behavior across tenants can surface rogue clients hours before manual log review would.
Conclusion
The ScreenConnect campaign demonstrates how threat actors exploit the trust model of remote management ecosystems by weaponizing legitimate extension frameworks. While ConnectWise’s swift containment limited the blast radius, the episode serves as a reminder that securing the core application is insufficient without equal rigor applied to its plugin architecture. Organizations should integrate extension lifecycle management into their DevSecOps pipelines—a capability Grivyonx helps teams automate through continuous security validation and policy-as-code enforcement.
- #ScreenConnect
- #ConnectWise
- #remote access
- #supply chain
- #incident response
- #extension security



