ConnectWise Incident Lessons: Managing Credentials and Third-Party Integrations

A stolen ConnectWise Cloud Backup secret was used to sign in to hundreds of Microsoft 365 tenants. What happened, and how to manage third-party integrations.

Content

Make Your Applications Secure Today

Sign up for a personalized demo to see how DerScanner can meet your Application Security needs

In October 2026, attackers used a stolen credential from ConnectWise Cloud Backup to sign in to customers' Microsoft 365 environments. The access came through an integration customers trusted. Here is what happened, and how to control the credentials that connect other companies' software to yours.

  • Oct 15, 2026 the main wave of malicious sign-ins
  • ~1,000 tenants with sign-in activity from the attacker, per Huntress
  • 3 services suspended by ConnectWise during the investigation

What happened

ConnectWise Cloud Backup (formerly SkyKick) connects to customers' Microsoft 365 environments through a multi-tenant app. To do its job, a backup tool needs wide access to mail, files, SharePoint and Teams. According to Huntress, the attacker held the app's API secret, and anyone holding it can request access tokens in every tenant where the app is installed.

Date (2026) Event
Oct 15 A wave of sign-ins as the ConnectWise app from one hosting address. Huntress saw activity in almost 1,000 Microsoft Entra tenants, and over 300 succeeded. Microsoft also reported broad successful sign-ins from a malicious IP address.
Oct 15 In two tenants Huntress investigated, the app granted itself Global Administrator within minutes and added new secrets to other apps in the tenant.
Oct 16 ConnectWise published an advisory about unauthorized access to application identities in the Cloud Backup environment.
Oct 17 ConnectWise disabled the affected apps and suspended Cloud Backup, SaaS Security and Cloud Management.
Oct 19 to 20 No new malicious activity was seen. ConnectWise said its stored backup archives showed no evidence of unauthorized access, and it did not say how the credential was stolen.
Oct 21 Microsoft attributed the attack to Storm-0940, a group it describes as aligned with the Chinese state, and said the group tried to sign in to more than 2,250 tenants.

The counts grew during the investigation. CyberScoop reported that Huntress had initially confirmed unauthorized sign-ins in 162 tenants, and more compromises are expected outside the environments it can see.

Five lessons

  1. Your attack surface includes your vendors. The access came through software customers had approved, with rights they had granted.
  2. App credentials skip MFA. An app signs in with its own secret, without a user. Strong MFA for people did not stop these sign-ins.
  3. Broad rights mean broad damage. Every permission you grant an app is a permission an attacker gets if its credential leaks.
  4. Attackers dig in fast. New admin roles and new secrets appeared within minutes. Disabling the original app does not remove them.
  5. Some access leaves no trace. Huntress noted that directory reads through Microsoft Graph may leave no audit record. A clean log is not proof of no access.

The point for every team. A trusted integration is a standing connection into your environment, held by someone else. Manage it as carefully as an admin account.

If you used ConnectWise Cloud Backup

This summary follows Huntress' guidance. Follow ConnectWise's advisory for the latest steps.

  1. Disable, do not delete, the affected apps. Huntress named Cloud Backup and the Cloud Management apps for Exchange Online, Teams and SharePoint Online. Do not re-enable them until ConnectWise confirms all credentials were reset.
  2. Check service principal sign-ins. Review sign-ins to these apps around Oct 15, 2026, including any from 144.172.64[.]128.
  3. Remove unexpected roles. Look for directory roles the apps assigned themselves, especially Global Administrator and Exchange Administrator.
  4. Review every app credential. Check secrets and certificates added to any app in your tenant since Oct 13. Disabling an app does not remove credentials already added elsewhere.
  5. Confirm your backups. Ask ConnectWise about retention and restore options while the service is suspended.

How to manage third-party integrations

These steps apply to any vendor app connected to your cloud or SaaS environment, not only ConnectWise.

  • Keep an inventory. List every third-party app with access to your tenant, who approved it, what rights it holds and who owns the relationship.
  • Grant the least rights. Check whether a vendor offers narrower permissions or per-mailbox scope. Remove apps you no longer use.
  • Limit who can approve apps. Require admin approval for new app consent, so integrations do not appear without review.
  • Alert on app changes. Watch for new secrets or certificates added to apps, and for apps that assign roles to themselves. Both happened here.
  • Ask vendors how they protect credentials. Where is the app secret stored, who can read it, how often is it rotated, and how fast will they tell you about a leak?
  • Have a response plan. Know how to disable an integration, review its activity and restore service, before you need to.

If you build integrations

Many software companies are on the other side of this story: they hold credentials that reach their customers' systems. That makes the security of those credentials part of the product. Keep app secrets in a secrets manager, never in source code or config files. Prefer certificates or short-lived tokens over long-lived secrets, separate production credentials from everything else, and scan every change for hardcoded secrets before it ships. We will take a closer look at secrets management in our next article.

Where DerScanner helps

DerScanner's SAST detects hardcoded credentials in your source code and configuration files. Export the report with the By secrets classification to see only the findings about sensitive data stored or leaked in the code, and compare it with an earlier scan to see which findings are new, which remain and which were fixed. DerScanner can run on-premises, so your code never leaves your network. Secret scanning protects the credentials in your own code; the steps above protect the connections other vendors hold into your environment.

Keep credentials out of your code

Book a demo and see a secrets-only report on your own project. Get a demo

Sources: Huntress blog, Oct 16, 2026, with updates to Oct 27 (huntress.com); CyberScoop, Oct 20, 2026 (cyberscoop.com); Microsoft Security Blog, Oct 21, 2026 (microsoft.com); The Register, Oct 19, 2026 (theregister.com); DerScanner User Guide, release 13.

Loading blogs...
Get Started

Ready to Reduce Technical Debt and
Improve Security?

Clean code. Fewer risks. Stronger software

dashboard