Executive Summary
In October 2026, ConnectWise disclosed unauthorized access to application identities associated with its Cloud Backup product (formerly SkyKick), a SaaS solution serving managed service providers (MSPs). A threat actor used compromised API credentials to authenticate into Microsoft 365 Entra tenants across more than 1,000 organizations, with over 300 successful sign-ins confirmed by third-party researchers at Huntress and Todyl. The attacker escalated privileges to Global Administrator in at least two tenants and planted persistent backdoor credentials. ConnectWise responded by disabling Cloud Backup, SaaS Security, and Cloud Management services while engaging an incident response firm and revoking compromised certificates.
This incident exemplifies the accelerating risk of supply-chain credential abuse targeting MSP platforms. Attackers increasingly exploit the trusted, high-permission relationships between SaaS vendors and their downstream customers, turning a single compromised vendor identity into a master key across hundreds of enterprise Microsoft 365 environments—amplifying blast radius far beyond what a direct breach would achieve.
Why This Matters Now
MSP-targeting supply chain attacks are surging in 2026, with threat actors systematically exploiting delegated SaaS credentials that grant Global Administrator access to thousands of downstream tenants simultaneously. Regulatory scrutiny under frameworks like NIST CSF 2.0 and CISA's Secure by Design initiative is intensifying, making vendor-side identity hygiene and third-party access governance an immediate compliance and operational imperative for any organization relying on managed services.
Attack Path Analysis
A threat actor obtained ConnectWise Cloud Backup application credentials (API secrets) from vendor-side infrastructure, enabling authenticated access to over 1,000 Microsoft 365 Entra tenants across MSP downstream customers. The attacker escalated privileges by granting Global Administrator roles to injected application identities, then moved laterally across tenant boundaries in strict tenant-ID order using a pre-built list, ultimately positioning for broad reconnaissance, data access, and persistent backdoor creation across policy, national security, trade, and critical mineral sector organizations before ConnectWise disabled the affected services.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
The attacker obtained ConnectWise Cloud Backup API secrets and application credentials — likely from vendor-side records or a supply chain breach of the ConnectWise platform itself. These valid credentials allowed the threat actor to authenticate as a trusted SaaS application across all consented Microsoft 365 tenants without triggering standard authentication alerts. No CVE exploitation was confirmed; the breach relied on valid stolen application identity credentials.
MITRE ATT&CK® Techniques
Valid Accounts: Cloud Accounts
Trusted Relationship
Use Alternate Authentication Material: Application Access Token
Account Manipulation: Additional Cloud Roles
Account Manipulation: Additional Cloud Credentials
Account Discovery: Cloud Account
Data from Cloud Storage
Data Destruction
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NYDFS 23 NYCRR 500 – Third-Party Service Provider Security Policy
Control ID: 500.11
DORA (EU Regulation 2022/2554) – ICT Third-Party Concentration and Dependency Risk
Control ID: Article 28 – ICT Third-Party Risk Management
NIS2 Directive (EU 2022/2555) – Supply Chain Security and Access Control
Control ID: Article 21 – Cybersecurity Risk Management Measures
CISA Zero Trust Maturity Model 2.0 – Application Identity and Privileged Access Governance
Control ID: Identity Pillar – Least Privilege and Continuous Validation
PCI DSS 4.0 – Risk Management of Third-Party Service Providers
Control ID: Requirement 12.8
ISO/IEC 27001:2022 – Information Security in Supplier Relationships and Supplier Service Monitoring
Control ID: Annex A 5.19 / 5.22
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
MSPs using ConnectWise Cloud Backup face supply-chain credential compromise across 1,000+ Entra tenants, exposing Exchange, SharePoint, and Teams data with lateral movement and exfiltration risk per NIST.800-53.SC-7.
Computer/Network Security
Security vendors Huntress and Todyl confirmed unauthorized Microsoft 365 tenant authentication via stolen ConnectWise API secrets, demanding zero-trust segmentation and egress policy enforcement per ZTMM.Network and PCI.4.0.3.5.1.
Financial Services
Downstream MSP clients in financial services face unconfirmed but probable tenant compromise, with Global Administrator privilege escalation threatening compliance under HIPAA.164.308(a)(3) and PCI.4.0.7.2.4 frameworks.
Government Administration
Huntress identified targeted reconnaissance against policy, national security, and critical mineral sector tenants in a manual sweep, indicating nation-state supply-chain interest requiring multicloud visibility per ZTMM.CrossCutting.Visibility.
Sources
- ConnectWise Disables Cloud Backups Amid Concerns for Downstream MSPshttps://www.darkreading.com/identity-access-management-security/connectwise-disables-cloud-backups-downstream-mspsVerified
- ConnectWise Cloud Backup Incident Disclosure Status Posthttps://www.connectwise.com/company/trust/security-bulletins/connectwise-cloud-backupVerified
- Huntress Security Blog: ConnectWise Cloud Backup Credential Compromisehttps://www.huntress.com/blog/connectwise-cloud-backup-credential-compromiseVerified
- Todyl Security Alert: ConnectWise SkyKick Backup Application Identity Compromisehttps://www.todyl.com/blog/connectwise-skykick-backup-application-identity-compromiseVerified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
This incident demonstrates how a single compromised SaaS application identity cascaded across more than 1,000 Microsoft 365 tenants, exploiting the absence of workload-level segmentation and identity-scoped access boundaries. Aviatrix Zero Trust CNSF would likely reduce attacker reachability by enforcing strict segmentation between vendor and customer environments, limiting the blast radius of a shared credential compromise.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: A Zero Trust fabric treating vendor application identities as untrusted by default could likely reduce the reachability of stolen credentials across downstream tenant environments, limiting how far a single compromised API secret may propagate through the MSP supply chain.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation enforcing least-privilege access boundaries could likely constrain the attacker's ability to propagate escalated privileges across segmented workload zones, reducing the operational scope of newly granted Global Administrator roles within cloud environments.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement between tenant-scoped workload segments could likely reduce the attacker's ability to freely pivot across customer environments, constraining sequential cross-tenant traversal by requiring explicit policy authorization for each lateral access path rather than inheriting access through a shared application identity.
Control: Multicloud Visibility & Control
Mitigation: Centralized multicloud visibility across cloud traffic paths could likely surface anomalous authentication sweep patterns from a single external IP, reducing the attacker's ability to conduct repeated cross-tenant credential sweeps undetected within the noise of legitimate SaaS API traffic.
Control: Egress Security & Policy Enforcement
Mitigation: Controlled egress policy enforcement governing outbound data paths from cloud workloads could likely constrain bulk data movement from consented M365 workloads toward external destinations, reducing the feasible volume of data that may exit across backup stores, mailboxes, and SharePoint environments under attacker control.
Had earlier segmentation and egress constraints reduced the attacker's lateral reach, the residual impact would likely involve a smaller number of affected tenant environments, limiting persistent backdoor deployment and reducing the number of critical-sector organizations facing active credential exposure and backup service disruption.
Impact at a Glance
Affected Business Functions
- Microsoft 365 Cloud Backup and Restore Services
- MSP-Managed Tenant Administration and SaaS Security Monitoring
- Exchange Online, SharePoint, OneDrive, and Microsoft Teams Data Access
- Cloud Management and Partner Identity Administration
Estimated downtime: 14 days
Estimated loss: N/A
The incident exposed application-level credentials (API secrets) tied to ConnectWise Cloud Backup, granting threat actors potential access to Microsoft 365 tenant data across MSP customer environments. Affected data categories include Exchange Online mailbox content, SharePoint documents, OneDrive files, Microsoft Teams messages, and Entra identity configurations. Over 1,000 Entra tenants were observed with sign-in attempts from the malicious IP address, with more than 300 successful authentications confirmed by Huntress. In at least two tenants, the attacker escalated the ConnectWise application to Global Administrator and established persistence by adding credentials for additional applications. A pre-built list of SkyKick partner tenant IDs is suspected to have been exfiltrated from vendor-side records, potentially exposing MSP partner metadata. The full scope of data access in live Microsoft 365 environments remains unconfirmed due to limited vendor-side visibility, but the breadth of permissions granted to the Cloud Backup application makes sensitive enterprise data exposure a significant concern across hundreds of downstream MSP-managed organizations.
Recommended Actions
Key Takeaways & Next Steps
- • Apply Zero Trust Segmentation (ZTMM.Network, NIST.800-53.AC-6) to enforce identity-based, least-privilege policies on all SaaS application identities — MSP-managed platforms must be segmented so a single compromised application credential cannot traverse all downstream tenant boundaries without re-authentication and per-tenant policy enforcement.
- • Deploy Multicloud Visibility & Control (ZTMM.CrossCutting.Visibility, NIST.800-53.AU-6) to establish behavioral baselines for SaaS application authentication patterns; anomalous bulk sequential tenant access from a single IP — a clear indicator in this incident — should trigger automated alerting and session termination across all affected tenants simultaneously.
- • Enforce Egress Security & Policy Enforcement (ZTMM.Data, NIST.CSF.PR.DS-5) on all cloud application outbound flows to prevent unauthorized data export via Microsoft Graph API or cloud storage copy operations; FQDN-level filtering and data loss prevention policies would limit the blast radius of credential abuse even after initial compromise.
- • Leverage East-West Traffic Security controls (ZTMM.Network, NIST.800-53.SC-7) to block cross-tenant lateral movement by enforcing workload-to-workload and service-to-service policy boundaries within MSP shared infrastructure; cross-tenant API calls should require explicit per-tenant identity verification rather than relying on a shared application secret.
- • Implement Cloud Native Security Fabric (CNSF) inline enforcement (ZTMM.CrossCutting.Automation, NIST.800-53.SI-4) as the primary control plane for real-time inspection of all cloud application authentication events and permission escalation attempts, ensuring that any application self-granting of Global Administrator roles triggers immediate automated revocation and incident response workflows.



