ScreenConnect Under Attack: Extensions and Clients to Check
ScreenConnect is under pressure from attacks exploiting third-party extensions and outdated clients: what changes for MSPs and companies.
The ScreenConnect case highlights a very real risk for those managing remote support and multi-client environments: when a tool becomes part of the operational chain, its abuse can quickly turn into a widespread problem. At this stage, it’s not just about a vulnerability to fix, but an ecosystem to secure: extensions, technical clients, active sessions, and granted privileges.
For businesses, MSPs, and IT managers, the message is simple: updating the server is not enough. If technicians’ clients lag behind, or if third-party extensions remain enabled without control, the infrastructure can remain exposed even after the main fix.
What Is Really Happening
The latest indications report malicious activity continuing to target mainly on-premises environments where some third-party extensions have not been disabled. ConnectWise has recommended upgrading technical clients to ScreenConnect 26.6.5 or later and immediately disabling the extensions identified as risky.
The critical point is that the problem does not coincide with a single software flaw. According to analyses shared by security vendors, attackers exploited extensions installed in partner environments to gain access, deploy unauthorized clients, and attempt propagation toward technicians’ workstations. This makes the attack surface broader than it might seem at first glance.
Why It Matters to Companies, Not Just MSP Providers
An attack on a remote support platform does not remain confined to the IT team using it. If an attacker manages to infiltrate the support channel, they can reach servers, endpoints, and environments of the customers served by that provider. In other words, an incident on the tool can become an incident on the digital supply chain.
For a company, this means three immediate risks:
- interruption of support and slowdown of operational activities;
- possible unauthorized access to remotely managed systems;
- exposure of credentials, sessions, and permissions accumulated over time.
The strategic lesson is that support tools should not be treated as simple utilities. They are high-criticality assets and deserve the same level of governance as VPNs, identity platforms, and endpoint management systems.
What to Do Immediately to Reduce Risk
The effective response is not limited to patching. A full environment review is needed, with separate attention to servers, technical clients, and installed integrations.
Operational Priorities
- verify that every technical client is updated to the required version or later;
- disable third-party extensions indicated by the vendor, especially in on-premises environments;
- monitor for anomalous activities such as unexpected commands, new administrators, unusual MFA prompts, and unauthorized remote access software;
- revoke active sessions and re-examine associated credentials and tokens;
- preserve logs for forensic verification of accesses, roles, and extension activities.
For many companies, the real test will be understanding whether the platform has been managed minimally or if, over the years, it has accumulated integrations and privileges no longer justified. The larger the perimeter has grown, the greater the operational risk.
The Real Stakes: Extension Hygiene and Visibility
This episode confirms a well-known but often underestimated trend: extensions increase productivity but also multiply trust points. Without an accurate inventory of what is installed, who manages it, and what permissions it holds, security becomes reactive rather than preventive.
For decision makers, the right question is not only “have we applied the patch?” but also “do we know exactly which third-party components can execute code, send commands, or bypass the normal authentication flow?” This is where control maturity is measured.
- Patching is necessary but not sufficient.
- Extensions must be treated as critical software.
- The technician’s client is a control point, not a detail.
- Active sessions must be considered potentially compromised.
- Visibility into logs determines the quality of the incident response.
,