ConnectWise, a leading provider of software for Managed Service Providers (MSPs), has confirmed it is investigating a security incident involving its ScreenConnect remote access solution. Reports indicate that threat actors have gained unauthorized access to the accounts of ConnectWise partners (MSPs) and are using that access to deploy malicious software to the MSPs' downstream customers. This constitutes a significant supply chain attack, leveraging the trusted relationship between MSPs and their clients. Due to the administrative power of Remote Monitoring and Management (RMM) tools like ScreenConnect, this compromise poses a severe risk, potentially enabling widespread, simultaneous intrusions across numerous organizations.
On November 11, 2026, ConnectWise acknowledged the incident after receiving reports from its partners about unauthorized activity. The core of the issue is the compromise of ScreenConnect accounts belonging to MSPs. Once attackers gain control of an MSP's ScreenConnect instance, they inherit the MSP's administrative access to all of their clients' managed endpoints.
The attackers are exploiting this powerful, trusted access to deploy unauthorized remote-access software within customer environments. This creates a secondary, persistent backdoor that the attacker controls directly, bypassing the MSP's infrastructure. While ConnectWise has not yet confirmed the initial access vector used to compromise the partner accounts, security researchers suspect that vulnerable third-party extensions installed within the ScreenConnect platform may be the root cause.
This attack leverages the inherent trust and power of RMM platforms, which are considered 'Tier 0' assets because they provide pervasive administrative control.
T1195.002 - Compromise Software Supply Chain. Alternatively, if partner credentials were stolen through other means like phishing, it would be T1078 - Valid Accounts.T1219 - Remote Access Software. The attackers are not breaking into each customer network individually; they are using the RMM as a force multiplier to pivot from one MSP to many clients.T1105 - Ingress Tool Transfer and T1574.002 - Hijack Execution Flow: DLL Side-Loading if the tool is deployed in a stealthy manner.The compromise of an RMM platform is one of the most impactful types of cyberattacks due to its cascading effects.
No specific IOCs were provided in the source articles.
For MSPs and their customers, hunting should focus on anomalous use of ScreenConnect.
log_sourceScreenConnect Audit Logscommand_line_patternpowershell.exe -enc or certutil.exe -urlcachecertutil to download external files.process_nameAnyDesk.exe, Splashtop.exe, TeamViewer.exefile_name*.mxt, *.mxt.zipD3-RAPA: Resource Access Pattern Analysis.D3-ACH: Application Configuration Hardening.M1033 - Limit Software Installation.Enforce MFA on all RMM accounts to prevent unauthorized access via stolen credentials.
Restrict access to the RMM management console to trusted IP addresses.
Implement a strict vetting and approval process for all third-party RMM extensions.
The most effective preventative measure against account takeover is the enforcement of multi-factor authentication (MFA) on all ScreenConnect accounts, especially those with administrative privileges. Even if an attacker manages to steal a partner's password through phishing or other means, MFA provides a critical second barrier to entry. MSPs must mandate non-phishable MFA methods, such as FIDO2 security keys or authenticator apps, for all technicians and administrators. This single control dramatically increases the difficulty for an attacker to gain unauthorized access to the RMM platform, thereby protecting the entire downstream customer base from this type of supply chain attack.
To detect an active compromise, MSPs must perform continuous analysis of RMM resource access patterns. This involves ingesting ScreenConnect audit logs into a SIEM and establishing a baseline of normal activity for each technician account. Alerts should be configured for deviations from this baseline, such as logins from new or unusual IP addresses/geolocations, access outside of normal working hours, or an abnormally high number of remote sessions. Furthermore, analyzing the types of commands executed during sessions can reveal malicious intent. For example, a technician who normally only performs patching suddenly running discovery scripts or attempting to download files would be highly suspicious. This behavioral analysis can provide early warning of an account takeover.
MSPs must harden the configuration of their ScreenConnect instances. This includes restricting administrative access to the server console to a whitelist of trusted IP addresses, effectively preventing logins from the open internet. Additionally, a strict vetting process for all third-party extensions must be implemented. Each extension should be reviewed for security and business need before being installed. Disabling or removing unused or risky extensions reduces the attack surface of the platform. Finally, role-based access control (RBAC) should be meticulously configured to ensure technicians have only the minimum necessary privileges to perform their jobs, limiting the potential damage if an account is compromised.
ConnectWise discloses it is investigating reports of unauthorized access to partner ScreenConnect accounts.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.