2026-04-20 · 2026-Q2
Vercel Breach via Context.ai AI Tool Supply Chain
Should this run hold this key at all?
- Fixable
- Architectural
- Vendor response
- Unknown
- In the wild
- Yes
- Actor
- Attacker
Target
Vercel (Next.js hosting platform) via Context.ai (AI Office Suite)
Impact
Attacker accessed Vercel Google Workspace and internal systems, including environment variables for a "limited subset" of customer projects; stolen data offered for $2M on BreachForums by a ShinyHunters persona; downstream crypto projects scrambled to rotate API keys
Root cause
Context.ai employee infected with Lumma Stealer in February 2026; attacker abused the Context.ai Google Workspace OAuth application that a Vercel employee had granted "Allow All" enterprise scopes; OAuth token replay escalated into the Vercel tenant
Sources
Catalog
Cite this: AgentProv incident record: Vercel Breach via Context.ai AI Tool Supply Chain (2026-04-20). https://agentprov.com/incidents/2026-04-20-vercel-breach-via-context-ai-ai-tool-supply-chain
Related
- Also L1 · 2026-10-21LiteLLM 1.107.0 on PyPI and Docker Ships a Credential Stealer That Runs at Every Python StartupL1Credential
- Also L1 · 2026-10-17OpenCode Console Breach Exposes Users' Stored OpenAI, Anthropic, and Google API KeysL1Credential
- Also L1 · 2026-10-13IBM MCP Context Forge Shipped a Known JWT Secret, Letting Anyone Mint Platform Admin Tokens (CVE-2026-53709)L1Credential