Description
The incident demonstrates the risks associated with trusted, multi-tenant applications that connect service providers to customer cloud environments.
ConnectWise Cloud Backup uses application identities to integrate with Microsoft 365. According to investigators cited by CyberScoop, possession of the compromised application secret could allow an attacker to request access tokens in tenants where the application was installed, without requiring a separate approval action from each customer during the attack.
The reported activity extended beyond initial authentication. In some affected tenants, attackers reportedly used the application's privileges to elevate access and add credentials to other applications. This could create additional access paths that remain available even after the original application is disabled.
The incident affected the availability of several ConnectWise services. ConnectWise stated that existing backup archives remained encrypted and isolated, with no indication that the stored archives had been compromised. This statement does not establish whether live Microsoft 365 environments were affected or whether data was accessed in individual tenants.
Technical Description
The reported attack involved abuse of a sensitive application credential associated with ConnectWise Cloud Backup and its connected Microsoft 365 environments.
The principal components were:
Application secret abuse: An attacker used a compromised credential associated with a multi-tenant application to obtain access tokens.
Microsoft Entra ID authentication: Suspicious service-principal sign-ins were observed across customer tenants.
Microsoft Graph reconnaissance: Microsoft Threat Intelligence reported follow-on activity involving Microsoft Graph API.
Credential persistence: Attackers attempted to add credentials to service principals, potentially creating additional ways to authenticate.
Privilege abuse: Investigators reported that the application's existing privileges could enable access to mail and files across connected Microsoft 365 services.
Service suspension: ConnectWise disabled affected application connections and temporarily suspended integrated services to limit further risk.
The initial credential exposure mechanism has not been publicly established in the cited reporting. Therefore, the incident should be described as a compromise and abuse of an application credential, rather than attributing it to a specific vulnerability or exploitation method.
Attack Overview
The reported attack sequence can be summarized as follows:
An application credential associated with ConnectWise Cloud Backup became available to an unauthorized party.
The attacker used the credential to authenticate to Microsoft Entra ID and request access tokens for tenants where the application was installed.
Suspicious sign-ins occurred across multiple Microsoft 365 customer environments.
Follow-on activity included Microsoft Graph API reconnaissance.
In affected tenants, attackers attempted to add credentials to service principals and establish additional access paths.
ConnectWise disabled affected application connections and suspended related services while investigation and remediation continued.
The reporting establishes the credential abuse, suspicious authentication, and follow-on activity. It does not establish the exact method by which the original secret was obtained or confirm data exfiltration from every tenant with suspicious sign-ins.
Technical Analysis
Multi-tenant application trust
The central security issue was the level of access associated with a shared application credential. A multi-tenant application can provide legitimate services across many customer environments, but a compromised credential can create risk across that same trust relationship.
Investigators explained that possession of the secret could allow an attacker to request access tokens in tenants where the application was installed. This reduces the need to compromise each customer independently before attempting access.
Microsoft Entra ID sign-in activity
Huntress observed a wave of suspicious authentication beginning October 15, 2026. By late Saturday, its telemetry showed activity across almost 1,000 Entra tenants, with more than 300 sign-ins appearing successful. Huntress confirmed unauthorized sign-ins in 162 tenants within its visibility.
These figures describe different measures: suspicious sign-in activity, apparently successful authentication, and confirmed unauthorized access. A successful sign-in does not, on its own, prove that files or mail were accessed or exfiltrated.
Microsoft Graph reconnaissance
Microsoft Threat Intelligence reported that activity following the suspicious sign-ins included Microsoft Graph API reconnaissance. Graph can provide access to Microsoft 365 directory and service data, depending on the permissions granted to the identity.
This activity is important because it can help an attacker identify available resources, permissions, and further opportunities for access. Investigators should correlate Graph activity with the application identity, source IP, authentication records, and subsequent directory changes.
Additional credentials and persistence
Researchers reported attempts to add credentials to service principals in target tenants. In some tenants with post-compromise activity, the application reportedly elevated its privileges and added credentials to other applications.
Such changes can establish additional authentication paths. Consequently, disabling the original application does not necessarily remove every access route that may have been created during the incident.
Potential security-control bypass
CyberScoop reported that the application's privileged access could allow attackers to bypass security controls, including multi-factor authentication, for activity performed through the application credential.
This should not be interpreted as a general bypass of MFA for all users. Application-based authentication can operate differently from interactive user sign-in, and the incident concerned the privileges associated with the
ConnectWise containment and service interruption
ConnectWise disabled seven application identities on October 17, 2026, at 07:00 UTC and suspended Cloud Backup. It also suspended SaaS Security and Cloud Management as a precaution because they were integrated with Cloud Backup.
As of the October 20 advisory, remediation, credential replacement, and validation were ongoing. ConnectWise reported no successful threat activity in the environments it monitored after mitigations began at 05:00 UTC on October 17. It also stated that each potentially affected partner and customer tenant still required individual review.
The company reported no indication that other ConnectWise offerings beyond Cloud Backup and the two precautionarily suspended services were affected.
Indicators of Compromise (IOCs)
The following indicators were published in ConnectWise's advisory and technical guidance. They are intended to support authorized investigation of Microsoft 365 environments.
| IOC Type | IOC | Associated Activity / Purpose |
|---|---|---|
| IP Address | 144.172.64[.]128 | Published suspicious address for reviewing Microsoft 365 authentication and audit logs |
| IP Address | 144.172.64[.]60 | Additional IP indicator reported on October 18 |
| IP Address | 144.172.64[.]99 | Additional IP indicator reported on October 18 |
| User Agent | Python-urllib/3.12 | Scripting-client indicator associated with suspicious authentication activity |
| User Agent | python-requests/2.31 | Scripting-client indicator associated with the incident |
| Application Client ID | 506e08f9-6e9a-4da4-942b-a099a03644ae | ConnectWise Cloud Backup |
| Application Client ID | 2399d300-6fca-4e6a-a686-399fefe75b83 | ConnectWise Cloud Management |
| Application Client ID | 24205314-2b89-4e07-a2a4-579e898a5640 | Cloud Management - MS Teams |
| Application Client ID | b78f6a77-d4e5-46fb-87e5-d1648bd02519 | Cloud Management - Exchange Online |
| Application Client ID | 0de14c77-b9b0-4137-9360-34878a929827 | Cloud Management - MS Graph |
| Application Client ID | 412dcf96-176d-4b3a-a1b0-4981ad66971e | Cloud Management - Partner Center |
| Application Client ID | b2b55f5b-7758-4719-8d8f-88ae172e6bdb | Cloud Management - SharePoint Online |
Important IOC handling notes:
The three IP addresses should be searched in Entra sign-in logs, service-principal sign-ins, and Microsoft 365 audit records.
User-agent strings are supporting indicators, not proof of malicious activity. Legitimate administrative scripts can use the same clients.
Application client IDs identify the affected integrations; their presence in a tenant is not itself proof of compromise.
ConnectWise stated that it disabled the seven application identities at the vendor level. Administrators should independently verify the corresponding application state and investigate their own tenant.
No malicious file hashes or malware domains are included here because the cited sources did not establish them as indicators for this incident.
Potential Impact
Cross-tenant exposure: A compromised credential associated with a multi-tenant application can put multiple customer environments at risk.
Email and file access: Investigators reported that the application's privileges could enable access to mail and files across Microsoft 365 services.
Persistence: Additional service-principal credentials could preserve access after the original integration is disabled.
Privilege escalation: Changes to application permissions and credentials can increase the attacker's ability to operate within a tenant.
Potential data exposure: Mailboxes, SharePoint files, Teams data, and related cloud resources could be at risk depending on permissions and the activity performed.
Operational disruption: Suspension of Cloud Backup, SaaS Security, and Cloud Management affected backup jobs, archive access, restores, monitoring, and management functions.
Incident-response burden: Managed service providers may need to review their own tenant and every customer tenant they administer.
The compromise of an application credential and the presence of unauthorized sign-ins do not independently prove that every listed resource was accessed or that data was exfiltrated.
Recommendations
Immediate Actions
Disable affected application connections: Verify the seven published application client IDs in Microsoft Entra ID and keep affected applications disabled until ConnectWise provides formal restoration instructions.
Preserve evidence: Export Entra sign-in logs, service-principal sign-in logs, directory audit logs, Microsoft 365 audit records, and relevant SIEM telemetry.
Search suspicious IPs: Investigate
144.172.64[.]128,144.172.64[.]60, and144.172.64[.]99, including both successful and failed authentication events.Review service-principal activity: Identify unfamiliar token use, Graph API reconnaissance, application credential changes, new permissions, and unexpected consent grants.
Inspect persistence mechanisms: Review newly added secrets, certificates, federated credentials, application owners, role assignments, and other identities modified during suspicious activity.
Review Exchange Online: Investigate unexpected mailbox forwarding, inbox rules, transport rules, delegated mailbox access, and other changes associated with suspicious identities.
Assess data access: Distinguish successful authentication from confirmed resource access, modification, and potential exfiltration.
Coordinate credential remediation: Work with the service provider and incident-response team to replace affected credentials and remove unauthorized access paths.
Keep affected applications disabled: Do not reconnect or reauthorize integrations until ConnectWise publishes formal restoration instructions.
Preventive Actions
Maintain an inventory of enterprise applications, service principals, client secrets, certificates, permissions, and owners.
Apply least-privilege access to service principals and restrict application permissions to required resources.
Use managed identities, certificates, or other approved credential-management approaches where appropriate, and securely store and rotate application secrets.
Monitor service-principal sign-ins and directory audit events, particularly credential additions, permission grants, owner changes, and role assignments.
Alert on unexpected Microsoft Graph access, unusual authentication locations, unfamiliar automation clients, and changes to cloud application identities.
Review third-party integrations for broad multi-tenant permissions and document the procedure for emergency revocation.
Retain cloud authentication and audit records centrally so investigators can examine activity before and after an incident.
Establish a formal third-party incident-response process that includes customer notification, evidence preservation, credential rotation, and tenant-by-tenant validation.
Conclusion
The ConnectWise Cloud Backup incident illustrates how compromise of a shared application credential can create risk across multiple customer environments. Reported attacker activity included suspicious Entra ID sign-ins, Microsoft Graph reconnaissance, and attempts to add credentials to service principals to maintain access.
The response requires more than disabling the original integration. Administrators must review authentication records, inspect directory changes, investigate other identities, and verify that unauthorized credentials and permissions have been removed. Managed service providers should perform these checks in both their own Microsoft 365 tenant and every customer tenant they administer.
As of October 20, 2026, the attacker had not been publicly identified, and the original credential-compromise mechanism remained under investigation. ConnectWise reported that stored backup archives remained encrypted and isolated, but this does not establish that live Microsoft 365 environments were unaffected. Tenant-specific investigation remains essential.
