Detect, Respond, Protect
See how the global Huntress SOC can augment your team
with 24/7 coverage and unmatched human expertise.
Start your free trial today.
Storm-0940 is a China-state aligned threat actor tracked by Microsoft and active since 2021. It targets organizations across many industries for data theft, using password spraying, exploitation of internet-facing applications, and abuse of OAuth applications in Microsoft 365 and Entra ID. Microsoft attributes the October 2026 ConnectWise Cloud Backup supply chain compromise to the group.
Microsoft describes Storm-0940 as a China-state aligned actor with no known industry aliases, active since 2021 and targeting organizations across multiple industries for data theft. Microsoft assesses that Storm-0940 was responsible for the October 2026 ConnectWise Cloud Backup supply chain compromise.
No leaders, operators or members of Storm-0940 have been publicly identified. Microsoft lists no known industry aliases for the actor, and no public reporting reviewed for this profile links it to a named individual, front company, or criminal brand.
Microsoft reports that Storm-0940 is one of many threat actors across multiple geographic regions using ARTEX, so use of that AI framework alone is not a reliable indicator of Storm-0940 involvement.
Microsoft says Storm-0940 targets organizations across multiple industries for data theft. Its tactical goals, as described by Microsoft, are:
Storm-0940 has historically used compromised applications to access and exfiltrate email and other data through Microsoft Graph. For the ConnectWise campaign, however, the presence of an affected application or a successful authentication does not by itself establish that customer data was accessed or exfiltrated.
Microsoft reported targeting across aerospace and defense, automotive, chemicals, energy, financial services, government, legal, manufacturing, media, military, semiconductor, software, technology, and think tanks and nonprofit organizations.
In the October 2026 ConnectWise campaign, Microsoft describes the following pattern:
144.172.64[.]99 sprayed 327 accounts across eight organizations, producing more than 151,000 failed logons, peaking at about 2,900 failures per minute on October 11. Microsoft observed no successful authentication in this run.In mid-October 2026, credentials for multi-tenant ConnectWise cloud applications (including ConnectWise/SkyKick Cloud Backup) were abused to authenticate to downstream customers' Microsoft 365 tenants through applications those customers had already authorized. Microsoft assesses that Storm-0940 was responsible and that it used ARTEX to accelerate scanning, password spraying, and OAuth application abuse. Microsoft states the activity did not result from a compromise of, or a vulnerability in, Microsoft corporate systems, products, or services.
144.172.64[.]99 against 327 accounts at eight organizations, with 151,000+ failed logons and no successful authentication.144.172.64.x range. ConnectWise’s initial October 16 advisory listed 144.172.64[.]128. ConnectWise added 144.172.64[.]99 and 144.172.64[.]60 in a subsequent October 18 update.Between October 13 and 16, 2026, Huntress observed related activity in separate phases: password spraying on October 13–14, unauthorized ConnectWise/SkyKick application sign-ins, and follow-on activity on October 15. Huntress’s observations are consistent with Microsoft’s account but do not independently verify Storm-0940 attribution or ARTEX use.
No arrests, indictments or sanctions against Storm-0940 were found in the sources reviewed for this profile.
Contain affected ConnectWise connections: Keep ConnectWise application connections disabled until ConnectWise issues formal restoration instructions. Do not delete the enterprise applications first. Preserve their configuration and evidence before making irreversible changes.
Inventory by application ID, not display name: Record the app IDs listed in the indicators section and each tenant's local service-principal Object ID. Review every tenant where the apps are or were ever installed or authorized, even if the integration is no longer used.
Preserve logs before remediating: Keep Microsoft Entra sign-in and audit records, Purview Audit records, SIEM data and any Microsoft Graph telemetry. Review activity from at least October 15, 2026, and extend service-principal sign-in review back to October 1 where records allow.
Audit credential, role and consent changes: Review Entra audit records for new credentials on applications and service principals, new applications, service principals or owners, app-role assignments, consent grants, privileged role assignments, and changes to users, groups, authentication methods and Conditional Access. Once evidence is preserved, have an authorized responder remove confirmed unauthorized credentials, grants and identities, and rotate credentials.
Apply least privilege to multi-tenant applications: Limit permissions and consent grants for vendor and multi-tenant apps to what the integration needs. High-privilege vendor apps are the access path this actor abused.
Verify that vendor remediation is complete: Confirm that vendor credential rotation and tenant-level cleanup removed all unauthorized access, since credentials added to other identities can outlive the compromised application.
Review mail and file activity: Look for unusual mail or file access, downloads, forwarding, inbox or transport rules, and delegated mailbox permissions.