Vercel Breach Linked to Context AI OAuth Hijack Exposes Customer Keys
Hackers used a compromised OAuth token from a Context AI app to hijack a Vercel employee’s Google account and access customer credentials.

TL;DR
Vercel says a compromised OAuth token from a Context AI app let attackers hijack an employee’s Google account and access internal credentials, which hackers say they are selling.
Context Vercel, a cloud platform for frontend frameworks, disclosed a breach after hackers posted claims on a cybercriminal forum that they had stolen customer API keys, source code, and database data. The actor claimed affiliation with the ShinyHunters group, which ShinyHunters denied. Vercel said the incident originated from a third‑party app made by Context AI, an AI‑evaluation tool.
Key Facts An employee installed Context AI’s Office Suite consumer app and connected it to their corporate Google account via OAuth, an open standard that lets applications access accounts without sharing passwords. Attackers abused that OAuth token to take over the employee’s Google account, then moved laterally into Vercel’s internal systems and retrieved unencrypted credentials. Vercel confirmed its Next.js and Turbopack open‑source projects were not affected. The company said it has notified impacted customers and advised rotation of any non‑sensitive keys and credentials in app deployments. Vercel warned the breach could affect “hundreds of users across many organizations,” suggesting downstream risk.
What It Means The incident illustrates a supply‑chain attack where a trusted third‑party application becomes a pivot point for credential theft. By exploiting OAuth token misuse (MITRE ATT&CK T1078.004), attackers bypassed traditional perimeter defenses and gained access to sensitive material without needing malware or phishing. The broad reuse of developer tools amplifies potential impact across the tech ecosystem.
Mitigations Security teams should: review and revoke unnecessary third‑party OAuth tokens; enforce MFA on all corporate accounts; monitor for anomalous token usage or impossible travel alerts; apply the principle of least privilege when granting app permissions; rotate credentials regularly, especially those stored in plaintext; and follow vendor advisories from Vercel and Context AI regarding token revocation and audit logs.
Watch for further details from Vercel’s investigation, any public advisories from Context AI, and signs of credential abuse in downstream services.
Continue reading
More in this thread
Vercel Breach Linked to Compromised Third-Party AI Tool Context.ai
Peter Olaleru
Vercel Breach Traced to Context AI OAuth Exploit, Warns of Hundreds Affected
Peter Olaleru
Revolution Dancewear Breach Exposes Data of Nearly 6,000 U.S. Individuals, Including 183 in Maine
Peter Olaleru
Conversation
Reader notes
Loading comments...