ConnectWise Investigates ScreenConnect Supply Chain Compromise

ConnectWise Probes ScreenConnect Partner Account Compromise

HIGH
November 15, 2026
6m read
Supply Chain AttackCyberattackIncident Response

Related Entities

Organizations

Products & Tech

Other

Managed Service Providers (MSP)

Full Report

Executive Summary

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.


Threat Overview

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.


Technical Analysis

This attack leverages the inherent trust and power of RMM platforms, which are considered 'Tier 0' assets because they provide pervasive administrative control.

  1. Initial Access: The initial vector is suspected to be the exploitation of a vulnerability in a third-party extension for ScreenConnect. This would fall under T1195.002 - Compromise Software Supply Chain. Alternatively, if partner credentials were stolen through other means like phishing, it would be T1078 - Valid Accounts.
  2. Execution & Lateral Movement: By using the legitimate functionality of ScreenConnect, attackers can execute commands and deploy software across all managed endpoints. This is a classic example of 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.
  3. Persistence: The deployment of a secondary, unauthorized remote access tool is a key step for the attackers. This ensures they maintain access to the customer environment even if the compromised ScreenConnect account is discovered and remediated. This aligns with T1105 - Ingress Tool Transfer and T1574.002 - Hijack Execution Flow: DLL Side-Loading if the tool is deployed in a stealthy manner.

Impact Assessment

The compromise of an RMM platform is one of the most impactful types of cyberattacks due to its cascading effects.

  • Widespread Customer Compromise: A single MSP breach can lead to the simultaneous compromise of hundreds or thousands of downstream customers, regardless of their own security posture.
  • High-Privilege Access: RMM tools operate with system-level privileges, giving attackers immediate administrative control over compromised endpoints. This allows for data exfiltration, ransomware deployment, and further lateral movement within the customer's network.
  • Systemic Risk to the MSP Ecosystem: Attacks like this undermine the trust-based model of managed services. Businesses rely on their MSPs for security, and when that trust is broken, it has far-reaching consequences for the entire industry.
  • Operational Disruption: Both the MSP and its clients face significant disruption as they work to identify, contain, and remediate the breach across potentially thousands of systems.

IOCs — Directly from Articles

No specific IOCs were provided in the source articles.


Cyber Observables — Hunting Hints

For MSPs and their customers, hunting should focus on anomalous use of ScreenConnect.

Type
log_source
Value
ScreenConnect Audit Logs
Description
Review for sessions initiated from unusual IP addresses, new admin accounts created, or sessions occurring outside of business hours.
Context
ConnectWise ScreenConnect server logs.
Confidence
high
Type
command_line_pattern
Value
powershell.exe -enc or certutil.exe -urlcache
Description
Look for ScreenConnect sessions executing encoded PowerShell commands or using certutil to download external files.
Context
EDR or command-line logging on managed endpoints.
Confidence
high
Type
process_name
Value
AnyDesk.exe, Splashtop.exe, TeamViewer.exe
Description
Monitor for the installation or execution of any remote access software that is not part of the corporate standard.
Context
EDR process monitoring and software inventory.
Confidence
high
Type
file_name
Value
*.mxt, *.mxt.zip
Description
Scrutinize any recently installed or modified third-party extensions for ScreenConnect.
Context
File integrity monitoring on the ScreenConnect server.
Confidence
medium

Detection & Response

  1. Audit RMM Sessions: All organizations using ScreenConnect or similar RMM tools must rigorously audit all administrative sessions. Look for logins from unfamiliar IP geolocations, sessions with unusual durations, and commands executed that are outside the norm for your technicians. This aligns with D3FEND's D3-RAPA: Resource Access Pattern Analysis.
  2. Inventory Extensions: MSPs should immediately create an inventory of all third-party extensions installed on their ScreenConnect servers. Check for any unauthorized or recently added extensions and research their reputation.
  3. Endpoint Monitoring: Customers of MSPs should have their own EDR and logging capabilities. Monitor for the installation of new software and the execution of scripts by the RMM agent. Alert on any activity that seems suspicious or is not part of a scheduled maintenance task.
  4. Account Security: Enforce MFA on all RMM accounts. Regularly review user accounts and permissions, disabling any that are no longer needed.

Mitigation

  1. Harden RMM Platforms: Treat your RMM platform as a Tier 0 asset. Restrict access to the management console to specific IP addresses. Enforce mandatory MFA for all users. This is an application of D3-ACH: Application Configuration Hardening.
  2. Vet Third-Party Extensions: Implement a strict policy for vetting and approving any third-party extensions. Only install extensions from reputable developers and, if possible, review their code for security flaws. This falls under M1033 - Limit Software Installation.
  3. Principle of Least Privilege: Configure RMM roles and permissions to grant technicians only the access they need. Avoid using a single, highly privileged account for all operations.
  4. Customer-Side Validation: End customers should not blindly trust all activity from their MSP's RMM tool. Use on-premises security tools to monitor the RMM agent's behavior and alert on actions that fall outside of the agreed-upon service contract, such as the installation of unknown software.

Timeline of Events

1
November 11, 2026
ConnectWise discloses it is investigating reports of unauthorized access to partner ScreenConnect accounts.
2
November 15, 2026
This article was published

MITRE ATT&CK Mitigations

Enforce MFA on all RMM accounts to prevent unauthorized access via stolen credentials.

Restrict access to the RMM management console to trusted IP addresses.

Audit

M1047enterprise

Continuously audit RMM session logs for anomalous activity.

Implement a strict vetting and approval process for all third-party RMM extensions.

D3FEND Defensive Countermeasures

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.

Timeline of Events

1
November 11, 2026

ConnectWise discloses it is investigating reports of unauthorized access to partner ScreenConnect accounts.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

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.

Tags

ConnectWiseScreenConnectsupply chain attackRMMMSPincident response

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.