top of page

708-575-1566

Your Backup Vendor Just Got Breached: What the ConnectWise Attack Means for Chicago Businesses

orio1985
Oct 23
5 min read


A cloud backup connection under review, with a fractured shield representing third-party supply-chain risk for Chicago businesses


A trusted backup app can become a path into your Microsoft 365 environment without anyone needing to type a stolen password. That’s the uncomfortable lesson from the ConnectWise Cloud Backup incident.

Why This ConnectWise Supply Chain Attack Matters to Chicago Businesses

ConnectWise published its initial advisory on October 16, 2026, about attempted unauthorized access associated with Cloud Backup, formerly SkyKick. Microsoft’s October 21 Security Blog attributed the compromise to Storm-0940, a China-state-aligned actor active since 2021 and focused on data theft.[1][2]

Microsoft says the attackers abused OAuth application credentials and the trust customers had already granted the backup app. This wasn’t a case of someone signing in as an employee with a stolen password. Because the access came through a trusted app relationship, there may not have been an interactive user sign-in to flag.

The campaign also shows how quickly threats can move. Microsoft reported ARTEX, an open-source, multi-agent AI penetration-testing framework, was used to automate attacks from reconnaissance through data exfiltration with little human interaction. The actor attempted sign-ins to more than 2,250 Microsoft 365 tenants at roughly 2,900 attempts per minute.

A separate cross-tenant password spray between October 10 and 14 produced 151,000+ failed logon events. Lockout responses represented nearly 98% of that activity, and Microsoft observed no successful authentication in the spray itself. That distinction matters: the password-spray statistics do not prove those accounts were accessed.

Microsoft did observe follow-on activity in some downstream customer environments, including reconnaissance through Microsoft Graph, application credential changes, and attempts to change identities, groups, and privileged roles. In one observed action, an application assigned itself the Global Administrator role.

At the same time, Microsoft cautions that the presence of an affected application, or even successful authentication, does not by itself mean customer data was accessed or exfiltrated. That’s why this calls for careful investigation, not assumptions.

A trusted cloud application connected to business tenants, with one permission pathway flagged for review

For Chicago law firms, CPA practices, healthcare providers, and manufacturers, the practical issue is clear: backups are not just a compliance checkbox. They’re part of a chain of vendors, permissions, and business-critical systems. HIPAA-regulated and client-confidentiality workloads need more than a “backup is on” status.

And a vendor being big, trusted, and popular is not a security control. The vendor owns its security failure. Your business still owns the risk of what happens inside your Microsoft 365 tenant.

Three Practical Moves for Your Backup and IT Providers

1. Ask who is actually holding your backups

Start with the question at the heart of this incident: Who is actually holding my backups, and can they prove it?

Ask your backup provider and IT partner

  • Which company operates the backup platform, and which other vendors or services does it depend on?

  • What access does its application have in our Microsoft 365 tenant, and how is that access limited?

  • If the service is interrupted or an application identity is compromised, who investigates our tenant, and what evidence will we receive?

Ask for clear answers about responsibility, notification, investigation support, and restoration procedures. If you use outsourced IT in Chicago, make sure your IT provider can explain who monitors vendor advisories and who takes action when a trusted connection is at risk. For most small business IT support in Chicago, nobody has ever asked them this, and the answer shows up in the next incident.

2. Hold vendors accountable for access, not just uptime

A vendor should be able to explain what permissions its app needs, why it needs them, how it monitors those permissions, and how it will help you investigate suspicious activity. Least privilege matters: multi-tenant app permissions should be limited to what the service requires.

Also clarify the division of work. Who checks your Microsoft 365 tenant? Who preserves logs? Who identifies new application credentials or privileged role assignments? A vendor’s containment action does not automatically remove changes that may already have occurred in a customer tenant.

This is where responsive managed IT services in Chicago can help connect the dots between the backup provider, Microsoft 365, and your internal team. Look for an MSP in Chicago that can explain its process plainly, rather than simply forwarding a vendor notice. An IT company in Chicago worth keeping will already know which application identities touch your tenant and what they can reach.

3. Do this this week: Review your Microsoft 365 tenant

Microsoft recommends customer-side checks. Have your IT administrator or security provider work through these steps in each relevant tenant:

  • Keep affected application connections disabled until ConnectWise provides formal restoration instructions.

  • Inventory the affected application IDs. Review every tenant where those apps are, or were, authorized, including integrations you no longer use.

  • Check service principal sign-ins and Entra audit records. Look for unexpected app activity, newly added application credentials, or new privileged role assignments.

  • Review Microsoft 365 audit logs. Check for unusual mailbox forwarding, inbox rules, delegated permissions, and unexpected email or file access.

  • Preserve evidence before deleting anything. Save relevant records and coordinate any removal of unauthorized credentials or permissions with an authorized responder.

  • Apply least privilege. Review whether multi-tenant application permissions are broader than needed.

A successful application sign-in does not prove data was accessed. But it is a reason to investigate what happened next, especially Graph activity and changes to credentials or roles. If you find suspicious activity, involve your security provider and follow ConnectWise’s current Cloud Backup advisories and guidance.[2]

A business IT team reviewing cloud identity activity, audit records, and a response checklist

Bigger Picture

A backup isn’t just about restoring files; it’s about knowing which vendors and identities can reach your business data. This incident is a reminder that vendor accountability, clear permissions, and a tested response plan are part of protecting client trust, patient information, and day-to-day operations.

Your Takeaway

Block off one hour this week to identify your backup provider, document its Microsoft 365 permissions, and confirm who will investigate your tenant if the service is disrupted. Don’t wait for an audit or a renewal conversation.

GCMSP provides local IT support in Chicago, including 24/7 monitoring, and reports 99.98% uptime, 95% of issues resolved in under an hour, and zero HIPAA violations in 2025. We also offer bilingual Spanish support for Chicago-area businesses. For practices looking for HIPAA-compliant IT services, see our healthcare IT support; for firms seeking IT support for law firms in Chicago, start with our industries we serve.

Want to see how your backup connections and Microsoft 365 permissions measure up? Let’s compare your current setup with practical next steps. Explore GCMSP’s Chicago managed IT support services or visit gcmsp.com to start the conversation.

Sources

Comments


Ready to Be Confident in Your Safeguards?

Do not wait for an audit or a breach. Schedule a conversation and get clear on what is protecting, or exposing, your patient data.

bottom of page