Compromised Context.ai OAuth Tokens Linked to Unauthorized Access at Vercel
Summary
Vercel reported unauthorized access after an employee’s Google Workspace account was accessed through compromised Context.ai OAuth tokens. The article outlines potential exposure and steps for organizations to find and revoke the app’s access, investigate activity, and,
Key points
- Context.ai said OAuth tokens for some consumer users were likely compromised; at least one Vercel employee had authorized the application with broad “Allow All” permissions.
- The article says the stolen token enabled access to Vercel’s Google Workspace. The potential infostealer link to Context.ai’s internal access remains unconfirmed.
- An actor claiming ties to ShinyHunters claimed responsibility for the Vercel incident, but the claim is unverified and could be impersonation.
- Organizations are advised to identify and revoke Context.ai access in Google Workspace, Entra ID, and Okta, and rotate affected users’ credentials and tokens.
- Investigate account, sign-in, and service activity for anomalies, including unexpected API activity, unfamiliar source IPs, and access to cloud environments.
- Vercel customers are advised to review activity and deployments, rotate environment variables that may have been accessible, and rotate Deployment Protection tokens. Sensitive variables limit exposure but do not undo prior access.
Article Details
- Victim Organization
- Vercel
- Incident Type
- Unauthorized access to Vercel's internal systems through a compromised employee Google Workspace account and a third-party OAuth application.
- Disclosure Date
- 2026-04-19
- Data Types Exposed
- OAuth tokens
- Operational Impact
- The attacker used a stolen OAuth token to access Vercel's Google Workspace. The article does not confirm data access, exfiltration, or operational disruption.
- Claim Status
- confirmed
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| HOSTNAME | 110671459871-30f1spbu0hptbs60cb4vsmv79i7bbvqj[.]apps[.]googleusercontent[.]com | OAuth application hostname identified as the compromised Google Workspace application linked to the incident. |
Threat Actors
Vendors
Products
Azure ADContext.ai offered Azure AD SSO integration configured as a per-tenant SAML SSO application. Search by name or by Context.ai's Entra tenant identifiers:Context.aireport, the attacker compromised an employee’s Google Workspace account via a third-party AI tool named Context.ai, who have since confirmed that their consumer-focused AI Office Suite environment was indeedEntra IDAzure / Entra ID:Google Workspacetheir internal systems. According to their incident report, the attacker compromised an employee’s Google Workspace account via a third-party AI tool named Context.ai, who have since confirmed that theirOktaOkta sign-in logs (if Context.ai was found as an Okta app):VercelOn April 19th, 2026, Vercel disclosed a security incident involving unauthorized access to their internal systems. According to their incident report, the attacker compromised an employee’s Google Workspace account via