<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oauth-Compromise on CuraSec</title><link>https://curasec.metacog.co.kr/tags/oauth-compromise/</link><description>Recent content in Oauth-Compromise on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Oct 2026 14:33:13 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/oauth-compromise/index.xml" rel="self" type="application/rss+xml"/><item><title>ConnectWise Suspends Cloud Backup After M365 Tenant Compromise</title><link>https://curasec.metacog.co.kr/insights/2026-10-18-connectwise-suspends-cloud-backup-after-attackers-compromise/</link><pubDate>Sun, 18 Oct 2026 14:33:13 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-18-connectwise-suspends-cloud-backup-after-attackers-compromise/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If ConnectWise Cloud Backup or any of the seven disabled application identities are authorized in your Azure AD/Entra tenant, immediately revoke those OAuth consent grants and audit M365 unified audit logs for unauthorized data access using the published application identity GUIDs.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Hunt M365/Entra audit logs for activity by the compromised ConnectWise application identity GUIDs (e.g., 506e08f9-6e9a-4da4-942b-a099a03644ae) — focus on anomalous OAuth token issuance, mailbox access, and SharePoint reads since the earliest possible compromise window.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Confirm whether ConnectWise Cloud Backup or related products are used by your organization; if so, request ConnectWise&amp;rsquo;s incident report, assess M365 tenant exposure, and evaluate whether any data access triggers breach-notification obligations.&lt;/li>
&lt;/ul></description></item></channel></rss>