Poisoned Pipeline

Poisoned Pipeline / Incidents / AS329

AS329 · 2026-10

Stolen ConnectWise Cloud Backup application identities signed in to customer Microsoft 365 tenants

Azure

ConnectWise disclosed unauthorized access to application identities in
Cloud Backup, formerly SkyKick. At 07:00 UTC on 17 October 2026 it
disabled seven multi-tenant application identities and revoked the
certificates used for those connections. The Cloud Backup application
client id is 506e08f9-6e9a-4da4-942b-a099a03644ae. Older installs may
still show SkyKick Cloud Manager names; ConnectWise says to match the
application id. Vendor-side disablement does not change the enterprise
application inside a customer tenant, and tokens already issued can
remain usable until they expire. ConnectWise also suspended SaaS
Security and Cloud Management because they share that environment.
It reports no evidence that encrypted backup archives were accessed,
and it says the product design does not let it see whether a customer
Microsoft 365 tenant was touched. The investigation was still open in
the 18 October remediation guide. How the application identities were
taken is not in that guide.

On 21 October Microsoft Threat Intelligence assessed that Storm-0940,
a China-aligned actor, was responsible for the compromise, and that
the actor used the ARTEX agentic penetration-testing framework to
speed it up. Microsoft says the actor attempted to sign in to more
than 2,250 tenants with the stolen application credentials, from the
same 144.172.64.0/24 range ConnectWise published (144.172.64.128,
144.172.64.99, 144.172.64.60). The applications had already been
granted access, so the sign-in did not need an interactive user.
Microsoft observed follow-on Microsoft Graph activity in multiple
customer environments, including reconnaissance, application
credential changes, and attempts to change privileges. In some
environments the actor enumerated cloud resources and read secrets
across Azure Key Vaults, including a key-unwrapping operation.
Microsoft also says a successful sign-in does not by itself mean
customer data was read, and that this was not a compromise of
Microsoft's own products. ConnectWise's archive finding and
Microsoft's Key Vault finding are different stores.

Huntress reported the same vendor-credential abuse against Microsoft
365 tenants. On 22 October Wiz described the same actor, overlapping
Storm-0940, using ARTEX against other IT and software vendors'
identity providers (Okta, Entra, Cognito) and Microsoft 365
integrations. That post is attempted expansion, not a second
completed vendor compromise.

Mapped techniques

supply-chain ConnectWise application identities

T0114 · Initial Access · Compromised service account

Unauthorized access to seven Cloud Backup application
identities. Customers who had already consented to those
apps could be signed into without an interactive user.
The vendor notice does not say how the identities were taken.

post-supply-chain Customer tenants that had granted the apps

T0165 · Persistence · Create access token

Microsoft observed application credential changes in multiple
customer environments after the stolen app signed in. The
ConnectWise guide tells tenants to look for added service
principal credentials. Not established for every tenant that
only saw a sign-in attempt.

T0199 · Impact · Secret leak

Microsoft says that in some environments the actor read
secrets across Azure Key Vaults and performed a
key-unwrapping operation. ConnectWise separately reports no
evidence that backup archives were accessed.

Framework gaps noted

Sources