Storm-0940's AI-Powered Supply Chain Attack: How Agentic AI Breached 2,250 Microsoft 365 Tenants Through ConnectWise
Executive Summary
In October 2026, Microsoft attributed a large-scale supply chain attack against ConnectWise Cloud Backup to Storm-0940, a China-linked threat actor. Exploiting compromised application credentials tied to ConnectWise's authorized Microsoft 365 integrations, Storm-0940 deployed an agentic AI penetration-testing framework called ARTEX to automate reconnaissance, password spraying, and OAuth application abuse at scale—targeting more than 2,250 downstream customer tenants across manufacturing, aerospace, energy, defense, and financial services. In several cases, attackers achieved privileged cloud persistence in under three hours, generating up to 2,900 sign-in attempts per minute. ConnectWise suspended its Cloud Backup, SaaS Security, and Cloud Management services in response.
This incident marks a watershed moment in AI-enabled offensive operations. Storm-0940's use of ARTEX demonstrates that nation-state actors are now weaponizing agentic AI to exponentially accelerate attack timelines, compress defender response windows, and scale supply chain compromise across thousands of organizations simultaneously—elevating the urgency of zero trust, segmentation, and multicloud visibility controls.
Why This Matters Now
Agentic AI is actively lowering the barrier and accelerating the pace of nation-state supply chain attacks. Storm-0940's use of ARTEX to generate nearly 3,000 sign-in attempts per minute compresses defender response windows to minutes, not days. As AI-enabled offensive tooling proliferates, organizations relying on MSP integrations with broad cloud access face immediate, elevated risk requiring urgent zero trust and egress enforcement investments.
Attack Path Analysis
Storm-0940, a China-linked threat actor, compromised ConnectWise Cloud Backup application identities to gain authorized access to over 2,250 Microsoft 365 downstream customer tenants, leveraging an agentic AI penetration-testing framework called ARTEX to automate reconnaissance, password spraying, and OAuth credential abuse at scale. Within hours of initial targeting, the attackers escalated privileges across multiple tenant environments, moved laterally through Microsoft Graph APIs, established persistent command-and-control footholds via modified application credentials, and positioned themselves for data access and potential exfiltration, ultimately disrupting ConnectWise Cloud Backup services and leaving hundreds of organizations without verified backup coverage.
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
Storm-0940 obtained or abused compromised application credentials associated with ConnectWise Cloud Backup, a supply chain vector that provided pre-authorized OAuth access to thousands of downstream Microsoft 365 tenant environments. ARTEX automated sign-in attempts against more than 2,250 tenants at up to 2,900 attempts per minute, exploiting the trusted application identity to bypass standard authentication scrutiny.
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Valid Accounts: Cloud Accounts
Brute Force: Password Spraying
Account Manipulation: Additional Cloud Credentials
Use Alternate Authentication Material: Application Access Token
Account Discovery: Cloud Account
Data from Cloud Storage
Forge Web Credentials: SAML Tokens
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev 5 – Supply Chain Risk Management
Control ID: SA-12 / SR-6
CISA Zero Trust Maturity Model 2.0 – Privileged Access and Credential Governance
Control ID: Identity Pillar — Least Privilege Access
NIS2 Directive – Supply Chain Security and Incident Handling
Control ID: Article 21 — Security of Network and Information Systems
DORA (Digital Operational Resilience Act) – Third-Party Provider Oversight and Concentration Risk
Control ID: Article 28 — ICT Third-Party Risk Management
PCI DSS 4.0 – Management of Application and System Accounts / Third-Party Service Provider Risk
Control ID: Requirement 8.6 / 12.8
NYDFS 23 NYCRR 500 – Third-Party Service Provider Security Policy / Monitoring and Training
Control ID: Section 500.11 / 500.14
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
MSPs using ConnectWise face critical supply-chain exposure as Storm-0940 exploited compromised OAuth credentials, enabling AI-accelerated lateral movement and privilege escalation across 2,250 Microsoft 365 tenants in under three hours.
Defense/Space
Explicitly targeted by Storm-0940's ARTEX-driven campaign, defense organizations face nation-state exfiltration risks requiring Zero Trust segmentation and egress policy enforcement to satisfy NIST.800-53 and ZTMM compliance mandates.
Financial Services
Directly named as a Storm-0940 target, financial firms risk OAuth application abuse and unauthorized Microsoft 365 privilege changes, demanding multicloud visibility controls mapped to PCI.4.0 and NIST.CSF.DE.CM-7 requirements.
Chemicals
Identified as a targeted sector in Storm-0940's supply-chain attack, chemicals organizations face AI-automated credential compromise and east-west lateral movement risks requiring microsegmentation aligned to HIPAA and NIST.800-53.SC-7.
Sources
- Microsoft Links Storm-0940 to ConnectWise Supply Chain Attackhttps://www.darkreading.com/cyberattacks-data-breaches/microsoft-storm-0940-connectwise-supply-chain-attackVerified
- ConnectWise Cloud Backup Unauthorized Access Disclosurehttps://www.connectwise.com/company/trust/security-bulletinsVerified
- Microsoft Threat Intelligence: Storm-0940 Campaign Analysishttps://www.microsoft.com/en-us/security/blog/Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- MITRE ATT&CK: Supply Chain Compromise (T1195)https://attack.mitre.org/techniques/T1195/Verified
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.
Aviatrix Zero Trust CNSF is directly relevant to this incident because Storm-0940 exploited a trusted application identity to move freely across thousands of tenant environments with minimal friction. By enforcing identity-aware segmentation and restricting east-west reachability between workloads and tenants, Aviatrix would likely have reduced the blast radius and constrained the attacker's ability to pivot at scale across ConnectWise's downstream customer base.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The scale of automated OAuth abuse across thousands of downstream tenant environments would likely be constrained by fabric-level visibility that could flag anomalous access velocity and reduce the reachability of compromised application identities to only explicitly permitted workload boundaries.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation would likely constrain the attacker's ability to expand privilege scope beyond the initial OAuth access boundary, as workload-to-workload communication and API-driven credential modification paths could be restricted to only explicitly authorized identity and access flows within each segmented tenant context.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely reduce the attacker's ability to traverse tenant boundaries freely, as lateral movement paths between workloads and across tenant environments could be constrained to explicitly defined and monitored communication policies rather than relying on the implicit trust of a shared application identity.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility and control would likely improve the detectability of anomalous API-driven command patterns by surfacing unusual traffic volumes, unexpected API call sequences, or access patterns that deviate from known workload baselines, potentially reducing the attacker's ability to operate undetected through legitimate-looking Graph API channels.
Control: Egress Security & Policy Enforcement
Mitigation: Egress security and policy enforcement would likely reduce the attacker's ability to move large volumes of sensitive data out of tenant environments by constraining outbound traffic to only explicitly permitted destinations and data flows, limiting the practical exfiltration surface even where Graph API access had been established.
If earlier CNSF controls had reduced lateral movement across tenant boundaries and constrained privilege escalation scope, the number of tenants reaching the point of service disruption and persistent backdoor exposure would likely have been smaller, reducing the overall operational footprint of the incident and limiting the need for broad service suspension.
Impact at a Glance
Affected Business Functions
- Microsoft 365 Cloud Backup and Recovery Services
- IT Managed Service Provider (MSP) Operations
- Cloud Identity and Access Management (IAM)
- SaaS Security and Cloud Management Platforms
Estimated downtime: 14 days
Estimated loss: N/A
Application credentials associated with ConnectWise Cloud Backup were compromised, granting unauthorized access to Microsoft 365 environments across more than 2,250 downstream customer tenants spanning industries including manufacturing, aerospace, chemicals, energy, defense, and financial services. Exposed data categories include Microsoft 365 tenant configuration data, application credential material, OAuth tokens, audit and sign-in logs, privileged identity assignments, and potentially backed-up business data such as email, files, and collaboration content stored within Microsoft 365. In multiple confirmed cases, attackers achieved privileged cloud persistence within three hours of initial targeting, raising the risk of exfiltration of sensitive corporate intellectual property, financial records, and regulated business communications. Actual financial loss is unquantified at time of publication; however, the scale of affected tenants and the privileged access obtained indicate high potential for significant downstream financial and reputational harm.
Recommended Actions
Key Takeaways & Next Steps
- • Apply Zero Trust Segmentation (CNSF) to enforce identity-based, least-privilege policies on all OAuth application connections to Microsoft 365 and SaaS platforms, ensuring that compromised service-provider credentials cannot traverse tenant boundaries or escalate privileges without explicit policy authorization.
- • Deploy Multicloud Visibility & Control to baseline and monitor all Microsoft Graph API activity across tenant environments, enabling real-time detection of anomalous application credential changes, unusual privilege modifications, and high-velocity automated sign-in patterns consistent with ARTEX-style agentic AI tooling.
- • Enforce Egress Security & Policy Enforcement controls to restrict outbound API calls from cloud workloads to only approved FQDN destinations and service endpoints, limiting the ability of compromised application identities to exfiltrate data to unauthorized external locations via Graph or storage APIs.
- • Activate East-West Traffic Security controls to inspect and govern service-to-service and application-to-tenant lateral flows, preventing a compromised supply chain application identity from being used as a pivot point to access workloads or data stores across multiple downstream tenant environments.
- • Leverage the Cloud Native Security Fabric (CNSF) with inline enforcement and distributed policy to detect and block agentic AI-driven attack automation, including high-frequency OAuth abuse and automated credential spraying, by enforcing rate-aware behavioral policies and real-time inspection at the cloud control plane layer.
