<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>M365 on CuraSec</title><link>https://curasec.metacog.co.kr/tags/m365/</link><description>Recent content in M365 on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:34:51 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/m365/index.xml" rel="self" type="application/rss+xml"/><item><title>Huntress Tragic Quadrant: Ranking Threats Hitting Businesses Hardest</title><link>https://curasec.metacog.co.kr/insights/2026-10-27-the-huntress-tragic-quadrant-ranking-threats-hitting-busines/</link><pubDate>Tue, 27 Oct 2026 16:34:51 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-27-the-huntress-tragic-quadrant-ranking-threats-hitting-busines/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The focus on legitimate-tool abuse and M365 session hijacking is worth understanding for defensive architecture, but the summary provides no specific CVE, misconfiguration, or patch target to act on.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> A ranked threat-technique overview could sharpen triage priorities, but the summary names no specific TTPs, IOCs, or ATT&amp;amp;CK mappings — read the full report before deciding whether any detections warrant tuning.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Microsoft 365 Token-Replay AitM Campaign Hits 79 Organizations</title><link>https://curasec.metacog.co.kr/insights/2026-10-26-microsoft-365-token-replay-attacks-compromise-97-accounts-at/</link><pubDate>Mon, 26 Oct 2026 17:20:31 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-26-microsoft-365-token-replay-attacks-compromise-97-accounts-at/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Active AitM campaign bypasses MFA via stolen session tokens — no patch exists, but hardening is actionable: enable Entra ID Token Protection in Conditional Access policies and audit sign-in logs for anomalous token-replay patterns since July 14, 2026.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Huntress documented 497 confirmed M365 sign-in events across 79 orgs from July 14–September 22, 2026; sweep Entra ID and M365 unified audit logs for token reuse from mismatched IP geographies or device states consistent with AitM relay behavior.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> M365 email accounts at 79 organizations were compromised via session-token hijacking — brief leadership now given M365&amp;rsquo;s ubiquity in your estate, confirm Entra ID token protection and phish-resistant MFA are enforced, and assess whether any internal accounts show anomalous sign-in activity.&lt;/li>
&lt;/ul></description></item><item><title>Storm-0940 uses AI tool ARTEX in ConnectWise supply chain attack on M365</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-ai-driven-large-scale-nation-state-campaign-using-artex-enab/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-ai-driven-large-scale-nation-state-campaign-using-artex-enab/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> ConnectWise supply chain compromise explicitly triggers Act; audit your M365 tenant for unauthorized OAuth app registrations and anomalous credential grants, and verify ConnectWise installation integrity against known-good baselines.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Active nation-state campaign with ATT&amp;amp;CK-mappable TTPs (supply chain compromise, application credential abuse); hunt for anomalous OAuth app registrations and unexpected delegated permission grants in M365 unified audit logs going back at least 90 days, and pull the full Microsoft post for Sentinel/Defender detection queries.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Nation-state supply chain compromise via a widely-used MSP tool affecting M365 tenants qualifies as a systemic event; verify whether ConnectWise is in your environment directly or via a managed service provider, request a formal exposure attestation from ConnectWise, and brief leadership given the nation-state attribution before they see it in the news.&lt;/li>
&lt;/ul></description></item><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><item><title>Compromised ConnectWise Credential Used to Access 173 M365 Tenants</title><link>https://curasec.metacog.co.kr/insights/2026-10-17-hackers-use-compromised-connectwise-credential-to-sign-in-to/</link><pubDate>Sat, 17 Oct 2026 14:12:31 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-17-hackers-use-compromised-connectwise-credential-to-sign-in-to/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If your org or your MSP uses ConnectWise Cloud Backup (formerly SkyKick), audit M365 unified audit logs and sign-in logs immediately for delegated-access activity from ConnectWise service accounts, and review/revoke any delegated admin permissions granted to ConnectWise.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Active campaign accessing M365 tenants via compromised MSP tool credentials — hunt M365 sign-in logs for authentication events tied to ConnectWise Cloud Backup service principals or delegated admin access since this campaign began, and alert on anomalous third-party delegated logins.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> If your organization uses an MSP that relies on ConnectWise Cloud Backup, confirm your exposure this week by requesting an attestation from that vendor; 173 confirmed tenant compromises via a single supply-chain credential is a board-question-level supply chain trust event.&lt;/li>
&lt;/ul></description></item></channel></rss>