Threat Actor Profile

Storm-0940

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.

Threat Actor Profile

Storm-0940

Attribution

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.

Leadership and members

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.

Storm-0940 TTPs

Tactics

Microsoft says Storm-0940 targets organizations across multiple industries for data theft. Its tactical goals, as described by Microsoft, are:

  • Gain initial access to cloud tenants at scale, including through compromised trusted third-party applications.
  • Establish persistence in Microsoft 365 and Entra ID environments by adding credentials to existing OAuth applications, so access survives remediation of the original foothold.
  • Reach privileged cloud access quickly. Microsoft observed multiple cases where the time from initial targeting to privileged access was under 3 hours.

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.

Techniques

  • Password spraying against Microsoft 365 and Exchange Online accounts, historically and in the October 2026 cross-tenant campaign.
  • Exploitation of internet-facing applications for initial access, followed by movement through the environment with compromised accounts.
  • Supply chain compromise of multi-tenant OAuth applications, then authentication to downstream customer tenants as the vendor application, without an interactive user sign-in.
  • OAuth application credential abuse: adding credentials to existing applications and service principals for persistence.
  • Privilege escalation in Entra ID, including an application assigning itself a high-privilege role such as Global Administrator.
  • Microsoft Graph and directory operations for reconnaissance and for changes to identities, groups and privileged roles.
  • Microsoft Defender for Cloud detected bulk secret reads across multiple Azure Key Vaults using a compromised multi-tenant application’s trusted access. The available reporting does not establish that these reads occurred in every ConnectWise-affected tenant.
  • Agentic AI tooling: ARTEX, an open-source multi-agent LLM framework written in Go with a Next.js frontend, that can use any AI model to run a penetration test from reconnaissance through data exfiltration with little human interaction.

Procedures

In the October 2026 ConnectWise campaign, Microsoft describes the following pattern:

  • Targeting at scale: Starting as early as September 2026, ARTEX was used against hundreds of organizations globally. Microsoft says the majority of targeting was not successful, but privileged cloud persistence was achieved at many organizations in a short time.
  • Password-spray run (Oct. 10–14, 2026): Infrastructure at 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.
  • Application credential abuse (from Oct. 15, 2026): Microsoft and Huntress associated different activity with addresses in the 144.172.64.0/24 range. Huntress identified 144.172.64[.]99 with the concentrated October 10–14 password spray and 144.172.64[.]128 with the primary vendor-application sign-ins. Huntress also reported a small number of failed user logins from 144.172.64[.]60.
  • Follow-on activity: In some tenants, the agents moved from authentication to Graph and directory operations, including reconnaissance, application credential modifications, and changes involving identities, groups, and privileged roles.
  • Persistence: Credential changes can remain active as a backdoor even after the original compromised application is remediated.

Want to Shut Down Threats Before They Start?

Notable Cyberattacks by Storm-0940

ConnectWise Cloud Backup Supply Chain Compromise (Oct 2026)

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.

What Microsoft reported

  • Oct. 10–14: A cross-tenant password-spray run from 144.172.64[.]99 against 327 accounts at eight organizations, with 151,000+ failed logons and no successful authentication.
  • Oct. 15: Public reports of the ConnectWise compromise surfaced, citing indicators in the same 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.
  • Following the compromise, the actor attempted sign-ins to more than 2,250 tenants, at up to 2,900 attempts per minute. Microsoft says the actor attempted sign-ins to more than 2,250 customer tenants, at a rate of up to 2,900 attempts per minute.
  • In multiple ConnectWise customer environments, activity progressed to Microsoft Graph and directory operations: reconnaissance, application credential changes for persistence, and changes to identities, groups, and privileged roles. One detection covered a ConnectWise application assigning itself the Global Administrator role.
  • Microsoft Defender for Cloud also detected bulk secret reads across multiple Azure Key Vaults using a compromised multi-tenant application's access.
  • Microsoft did not say how many customers were compromised, and notes that a successful authentication or an affected application does not by itself mean data was accessed or exfiltrated.

What Huntress observed

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.

Storm-0940 Law Enforcement

No arrests, indictments or sanctions against Storm-0940 were found in the sources reviewed for this profile.

  • Microsoft Threat Intelligence attributed the campaign publicly on October 21, 2026. Igor Tsyganskiy, an executive vice president at Microsoft, said on LinkedIn that a wave of AI-driven attacks has been ongoing since early October and that the ConnectWise incident is one of many.
  • ConnectWise published an initial advisory on October 16, 2026, and subsequently expanded its disclosures and containment guidance. As of October 23, ConnectWise was conducting restoration testing and security validation and had not yet completed phased restoration and re-enrollment.
  • As of October 23rd: ConnectWise was still conducting restoration testing and security validation. It advised partners to keep affected application connections disabled until service-specific restoration instructions were issued. Existing backup archives were reported as encrypted, isolated, and preserved, but restoration access and phased re-enrollment were still being brought back online.

How to Defend Against Storm-0940

1

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.

2

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.

3

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.

4

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.

5

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.

6

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.

7

Review mail and file activity: Look for unusual mail or file access, downloads, forwarding, inbox or transport rules, and delegated mailbox permissions.

References

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.

Try Huntress for Free