AIDEFEND in Action AIA-0135 Incident

Storm-0940: ConnectWise Application Credentials Enabled Downstream Tenant Persistence

Microsoft attributes ARTEX-assisted abuse of compromised ConnectWise application credentials to Storm-0940. Existing customer consent enabled app-only access; some tenants then experienced Graph reconnaissance, privilege changes and additional credentials on other applications. More than 2,250 tenants were targeted for sign-in, not all compromised. A separate 151,000-plus-event password spray had no observed successful authentication. Vendor containment did not automatically undo tenant-local persistence.

Supply Chain CompromiseService Principal TakeoverIdentity & AccessSaaS SecurityAgentic AI
7 applicable AIDEFEND defenses

Threat Analysis

  • Trust crossed the provider boundary: A valid vendor credential could exercise existing customer consent without interactive login. Microsoft attributes the campaign to Storm-0940’s ARTEX use; the provider’s original theft mechanism remains unknown.
  • Persistence moved to another identity: First-hand Huntress observations show directory elevation and added secrets on other tenant applications, with subsequent use of one added credential. Remediating the original vendor connection cannot undo those independent objects.
  • Attempts are not compromises: The 2,250-plus figure counts targeted sign-ins. The separate password spray failed. Successful authentication, directory activity and confirmed data access must be assessed separately. Supporting primary records: ConnectWise’s service advisory; Huntress’s tenant investigation.

Applicable AIDEFEND Defenses (7)

AID-D-011.004
Non-Human Identity & Delegated Token Abuse Detection
High
Correlate service-principal sign-ins, Graph activity, directory role/credential changes and downstream resources for each tenant-local object ID. Compare against approved vendor behavior and preserve lifecycle coverage gaps. Review beyond the published IPs: the documented credential changes did not all originate from the initial sign-in address.
AID-E-001.001
Root & Long-Lived Credential Object Eviction
High
ConnectWise, as owner of the original application credential, must invalidate it at its issuer and verify that all former consumers and authentication paths reject it. Customers can disable tenant access but cannot rotate a certificate private key held in the vendor tenant. Preserve evidence and coordinate replacement through the vendor’s current restoration process. Tenant administrators must separately remove confirmed attacker-added secrets or certificates on other applications. Re-fetch immutable application and credential IDs before each scoped action, preserve the audit record and prove new authentication with the added credential fails. Vendor key rotation does not perform this cleanup.
AID-E-001.002
Issued Token, Authentication Session & Lease Revocation
High
Inventory issued application tokens and affected authentication sessions. Use actual provider/resource revocation or denial capabilities and hold containment through expiry when immediate invalidation is unavailable. Prove rejection with controlled reuse, rather than inferring it from a credential or service-principal change.
AID-E-001.003
AI Agent & Workload Principal and Issuance Disablement
High
Disable the affected tenant-local service-principal access and fresh issuance path, preserving its configuration first. Read back the exact object and prove a new app-only authentication attempt fails. Reconcile provider-owned and customer-owned boundaries; a tenant disablement is not proof that the vendor has invalidated its credential globally.
AID-E-001.004
Delegated Grant & Connected-App Authorization Revocation
High
Remove app-role assignments, consents and delegated authorizations that sustain compromised application access, using their exact authoritative objects. A previously legitimate vendor consent can require revocation during containment; do not mislabel it as an attacker-created grant. Review every connected application and tenant in scope, then verify that the removed grants cannot support fresh access. Privileged directory role membership also needs the corresponding Entra role-assignment cleanup; do not mistake an OAuth-consent deletion for removal of every directory role.
AID-R-003.003
Progressive Capability & Privilege Re-enablement
High
Reauthorize only the vendor’s approved replacement application after tenant-local persistence review, with minimum required permissions and staged verification. ConnectWise’s November 4 instructions require new successful snapshots, not just a consent screen, to prove backups resumed. Keep old affected applications disabled unless explicitly instructed otherwise.
AID-H-004.001
User & Privileged Access Management
Medium
For the separate user-password route, enforce phishing-resistant MFA at the actual human identity boundary and test password-only and recovery paths. This constrains a future password-only success; it does not explain the already failed spray or protect application-only authentication with stolen vendor credentials.

What Defenders Should Do Now

  • Inventory applications by immutable IDs, including old SkyKick names and dormant consent. Preserve configuration and available audit evidence while urgently disabling affected access. Do not delete enterprise applications indiscriminately.
  • Coordinate provider credential invalidation with tenant-local key, issued-token, principal and grant cleanup. Review directory-role changes separately and verify each authoritative result. Human MFA is useful for the separate user route, not a remedy for app-only credentials.
  • Follow current ConnectWise restoration guidance for the replacement application. Verify tenant security before restoring permissions, then confirm successful new backup snapshots. A consent screen is not operational recovery.

Conclusion

AIDEFEND  separates the identity objects that must be detected, contained and removed, and the capabilities that can be restored only after verification. That distinction prevents provider-side rotation from being mistaken for complete tenant recovery.

Last updated: