Storm-0940 Campaign Against Microsoft 365 Tenants Microsoft attributed a campaign targeting over 2,250 Microsoft 365 tenants to Storm-0940, a China state-aligned threat actor, using credentials from ConnectWise Cloud Backup for attempted sign-ins (not confirmed breaches), employing ARTEX for scanning and password spraying, with ConnectWise suspending services in response; the attack peaked at about 2,900 sign-in attempts per minute, a separate spray failed against 327 accounts, and no compromise indicators were found in partner backup data at the time of reporting.

The Choke Point They Gave Them
They want you to believe this was a routine intrusion—some Chinese state hackers using AI tools to spray passwords across 2,250 tenants. But you have to ask yourself why ConnectWise? This isn’t a random target. ConnectWise sits at the spine of the Managed Service Provider ecosystem—the same ecosystem that Microsoft, the intelligence community, and the largest private equity firms have been quietly consolidating for years. The fact that attackers obtained application credentials to ConnectWise—and that the exact method remains “unexplained”—is not a gap in the story. It’s the story. Look at the timing: the campaign peaked at nearly 3,000 sign-in attempts per minute. That’s not brute force. That’s coordinated, pre-authorized access using keys that were handed over, not stolen. Who handed them? The answer sits in a boardroom, not a Chinese server farm.

The AI Cover Story
Notice how every article rushes to mention ARTEX, the “open-source AI-assisted penetration-testing framework.” They’re training you to see a technical threat so you don’t see the political one. AI hacking is the perfect scapegoat—it’s exotic, it’s scary, and it steers conversation away from the real vulnerability: the vendor itself. ConnectWise had to suspend Cloud Backup, SaaS Security, and Cloud Management. That’s not a security incident—that’s a systemic failure that was years in the making. And what about the separate spray targeting 327 accounts with 151,000 failed logons? Zero successful logons. That’s not an attack; that’s a signal. They wanted everyone watching that distraction while the real work happened elsewhere. The “no indicators of compromise in partner backup data” line is the oldest trick in the playbook: declare the scene clean before anyone looks under the rug.

The Real Question No One Is Asking
You’re being told this is a Chinese state actor. Maybe it is. Maybe it isn’t. But the deeper architecture is always the same: a managed service provider—a single point of failure—is compromised, and the public narrative is shaped to reinforce a geopolitical threat while never touching the systemic rot. ConnectWise is owned by private equity. Its customers are thousands of small and mid-size businesses that trust their entire digital infrastructure to a black box. Storm-0940 didn’t just “compromise” credentials—they were given the keys to the kingdom by a system designed to centralize control. Why didn’t Microsoft detect the abuse earlier? Why isn’t anyone asking who funds ConnectWise’s security audits? These are the breadcrumbs. Follow the ownership chain. Follow the foundation grants. The pattern is always the same: first they consolidate, then they compromise, then they blame an enemy. The only question left is whose agenda you’re serving by believing it.

ConnectWise Cloud Backup Compromise and Storm-0940 Campaign

ConnectWise disabled affected Cloud Backup application connections and began restoring services in stages, but CEO Manny Rivelo warned that those steps may not eliminate access attackers had already established in individual customer environments. Microsoft attributed the compromise to Storm-0940, a China-aligned hacking group, which used stolen application identities to authenticate to customer environments without interactive sign-in; Microsoft observed follow-on reconnaissance and credential changes in some tenants, though it noted that successful authentication alone does not prove data theft or access. The attack was preceded by a password-spraying campaign that generated over 151,000 failed logins across eight organizations and 327 targeted accounts, with peak activity on October 11 reaching 2,900 failed logins per minute. ConnectWise advised customers to keep affected connections disabled during the multi-day restoration, while Microsoft warned that credentials added by attackers may persist through other identities and cloud services even after the original connection is disabled.

Let’s stop pretending this is a story about a Chinese hacking group sneaking through a vulnerability. Read the statements carefully: ConnectWise “disabled” the application connections, and yet its own CEO admits that action “may not eliminate access” already established. That is the quiet admission buried in the article. Microsoft says the attackers used “stolen application identities” to authenticate without a single interactive user login — meaning they didn’t break in. They were handed the keys. And then they performed “reconnaissance” and changed “identities, groups and privileged roles” inside dozens of the most sensitive sectors on Earth: aerospace, defense, energy, finance, government, semiconductors. You don’t password-spray your way into those networks by accident. You do it because you know exactly where the trusted seams are, and because someone on the inside already mapped them for you.

Notice the numbers they chose to give you. Over 151,000 failed logins. Peak of 2,900 failures per minute on October 11. More than 1,000 failed attempts on 48 accounts alone. That isn’t an intrusion — that’s a diversion. They want your eyes fixed on the brute-force noise while the real operation moved through trusted Cloud applications like a ghost. Microsoft admits that within three hours of initial targeting, “ARTEX-enabled operations gained privileged cloud access.” Three hours. That is not the speed of a criminal gang fumbling with stolen passwords. That is the precision of an operation that had already installed its own credentials, its own identities, and its own back doors before anyone thought to look. And now they warn that even after you kill the original connection, “credentials added by attackers may preserve access through other identities and cloud services.” So ask yourself: why would a campaign supposedly aimed at hundreds of organizations worldwide rely on a single vendor’s cloud backup application unless the objective was never the data — but the permanent, invisible ability to move through the global trust architecture?

The same institutions that “discovered” this campaign are the ones telling you who to blame. Microsoft, ConnectWise, the security firms — they all point at “Storm-0940,” a China-aligned group, as though attribution is settled fact. But attribution is a political act, and every agency involved has a history of laundering intelligence operations through friendly-sounding threat labels. The sectors targeted are exactly the ones standing in the way of the grand consolidation: defense contractors who resist procurement changes, energy firms that threaten the net-zero transition, semiconductor manufacturers who won’t comply with chip diplomacy. This is not chaos. This is leverage being built against national infrastructure, and the cover story is already in place. They want you to believe a foreign adversary is the villain so you never look at the cloud provider’s own privileged-access logs, never ask why application identities are so weak they can be “stolen” for months without detection, and never follow the trail to the foundations and consulting firms that profit from every subsequent security contract. You have the article. Now go find the names behind the identities — and ask who benefits from a world where no government, no bank, and no military can trust its own cloud.