Oauth-Abuse on CuraSec

Russian Clusters Abuse Google OAuth and WhatsApp Linking to Hijack Accounts

Fri, 21 Aug 2026 11:38:25 +0000

Engineer — Learn: Describes a novel technique where threat actors weaponize legitimate OAuth device-authorization flows and WhatsApp multi-device linking to hijack accounts without traditional phishing; no patch exists but worth reviewing whether your OAuth app consent and device-link flows have anomaly logging enabled.
SOC/IR — Plan: Three named Russian espionage clusters are running active campaigns against academia, defense, and government targets using legitimate auth flows — build or tune detections for unusual OAuth device-code grant activity and unauthorized WhatsApp device registration events, and prioritize coverage if your org is in a targeted sector.
Leader — Learn: Nation-state espionage clusters are persistently targeting academia, aerospace/defense, government, and think tanks in the US and Europe; useful context for sector-specific threat briefings but no immediate leadership action is defined without disclosed IOCs or confirmed victim organizations.

Fri, 21 Aug 2026 11:38:25 +0000

Engineer — Plan: OAuth consent-flow abuse by APT29-linked clusters is a real attack surface for any organization using third-party OAuth integrations; audit configured OAuth app permissions and enforce stricter conditional access policies to reduce the social-engineering foothold these groups exploit.
SOC/IR — Act: Three active Russian clusters are running persistent campaigns against high-value sectors using OAuth flow hijacking and captive-portal redirects — pull Google’s full IOC list, hunt for anomalous OAuth token grants or device-code auth attempts since mid-2025, and tune detections for captive-portal redirect chains tied to UNC7005 TTPs documented by Reliaquest and Microsoft.
Leader — Plan: If your organization falls in academia, aerospace/defense, government, or think tanks, queue a targeted user-awareness briefing on OAuth and device-code phishing before next quarter; the APT29 lineage of UNC6293 elevates this beyond routine phishing and warrants a conversation with your security team about protective intelligence coverage.

Tue, 14 Jul 2026 12:08:08 +0000

Engineer — Plan: No platform CVE to patch — the attack surface is over-trusted OAuth connections and third-party integrations. Audit all connected apps in your Salesforce org, revoke unused OAuth grants, and review third-party vendor permissions this quarter.
SOC/IR — Act: Microsoft has detailed three concrete attack paths from an active, year-long campaign — hunt for anomalous OAuth authorization events and unusual connected-app activity in Salesforce audit logs going back at least 12 months to check for prior compromise.
Leader — Act: ShinyHunters is an active data-extortion group and this campaign abuses third-party SaaS trust, not software flaws — confirm your organization’s Salesforce OAuth integrations are inventoried, brief leadership on third-party SaaS risk exposure, and ask your Salesforce-connected vendors for attestation of their OAuth hygiene.

Tue, 14 Jul 2026 12:08:08 +0000

Engineer — Plan: ShinyHunters’ TTPs — OAuth app abuse and misconfigured guest access — directly affect cloud/SaaS configurations engineers own; no KEV or exploitation signals, but audit third-party OAuth app consent grants and tighten guest-access policies in your M365/IdP tenant this quarter.
SOC/IR — Act: Microsoft Threat Intelligence documents an active, named campaign; review the blog for IOCs and ATT&CK-mappable TTPs, then hunt for anomalous OAuth token grants and vishing-preceded MFA/auth events in identity logs since the publication date.
Leader — Plan: ShinyHunters’ supply-chain and OAuth abuse pattern against SaaS platforms warrants a SaaS vendor review this quarter — confirm key vendors enforce OAuth app allowlisting and have disabled unnecessary guest access — no specific named-vendor breach requiring immediate stakeholder communication.