ConnectWise has taken the drastic step of suspending its Cloud Backup service after attackers compromised the credentials of its backup application and used them to sign in to Microsoft 365 tenants belonging to the company's managed-service-provider customers. According to The Hacker News, which reported the story on October 17, 2026, the attackers reached as many as 173 customer tenants without needing a single stolen password or a phishing email.
What happened
The IT management software provider said it identified the issue on October 14, 2026, through what it called "advanced cybersecurity monitoring and diligence." On October 17 at 07:00 UTC, ConnectWise disabled seven affected application identities and revoked the certificates used by the compromised application connections across all users, effectively shutting off Cloud Backup access for partners and customers.
"Disabling the affected connections prevents new authentication through those connections; it does not reverse changes previously made inside a tenant," the company said in its advisory, as reported by The Hacker News. ConnectWise also cautioned that previously issued access tokens may remain usable until they expire, and that any unauthorized credentials or permissions the attackers created through separate identities would need additional review.
How the attackers got in without MFA
The most alarming part of this incident is the method. The attackers did not log in as users. Instead, they authenticated directly as the ConnectWise Cloud Backup application itself, using a stolen application secret to request Microsoft Graph tokens. As security vendor Huntress explained in an analysis covered by isec.news, those tokens inherit the application's pre-granted rights, which in this case were extremely broad.
The application, formerly known as SkyKick, had been granted standing access to mailboxes, OneDrive, SharePoint, Teams and directory data in every tenant where a managed service provider had installed it. Because application identities (service principals in Microsoft Entra ID) perform automated tasks like backups, they do not go through the same multi-factor authentication and Conditional Access checks as human users. The attackers' scripted sign-ins, originating mostly from the IP address 144.172.64.128 with Python-based user agents, simply bypassed MFA entirely.
How far the intrusion reached
Huntress confirmed unauthorized sign-ins in 162 tenants by 19:00 UTC on October 16, with the count rising to 173 in later reporting. In at least one detailed case, the attackers went further: another ConnectWise application assigned itself the Global Administrator role and added new credentials to two other applications, a classic persistence move. Notably, Huntress warned that directory reads through Microsoft Graph may not leave the same audit evidence as mail or file access, so the true extent of data exposure remains unclear.
ConnectWise said it has no evidence that stored backup archives were accessed, describing them as encrypted, isolated and preserved. However, the company admitted that scheduled backups are not running and that access to backup archives and restoration capabilities remains unavailable while the service is suspended. Out of caution, it also took its SaaS Security and Cloud Management products temporarily offline.
Why this matters for every business
This was not a perimeter breach, a ransomware deployment or a phishing campaign. It was an attacker authenticating as a trusted application, and Microsoft 365's standard identity defenses had nothing to say about it. The incident shows how much standing privilege third-party vendor applications can accumulate: one stolen secret inherited broad access to thousands of corporate tenants at once.
"Since implementing these mitigations, we have not observed successful threat activity in the environments we monitor," ConnectWise said, adding that this finding does not establish the status of downstream customer environments, which it cannot directly observe. Whether a product vulnerability contributed to the compromise is still under investigation.
What admins should do right now
If your organization uses ConnectWise Cloud Backup or works with an MSP that does, here are the steps security researchers recommend:
- Review service principal sign-in logs in Microsoft Entra ID for the listed ConnectWise application identities and the suspicious IP address.
- Audit application roles, secrets and certificates created or modified since October 13, 2026, and revoke anything unauthorized.
- Check for persistence: new application credentials, elevated role assignments, mailbox rules and other changes the attackers may have planted.
- Rotate vendor application secrets and confirm that backup and restore functionality is deliberately re-enabled only after ConnectWise clears it.
- Reduce standing permissions for third-party apps: grant only what they need, and require regular reviews of consented applications.
The bigger lesson, as the investigation continues, is that identity is now the perimeter. A vendor app with tenant-wide access is a tenant-wide risk, and defending it requires monitoring machine identities as closely as human ones.
Disclaimer: this story is developing; verify the latest status on ConnectWise's trust advisory page before taking action.



