Collections·4wVercel discloses security incident involving unauthorized internal access
A Vercel security breach in April 2026 was traced to a compromised OAuth token from Context.ai, a third-party AI tool connected to a Vercel employee's Google Workspace account. Context.ai had been breached via an AWS compromise and an infostealer infection, allowing attackers to use persistent OAuth tokens to access Vercel's internal systems. Attackers enumerated non-sensitive environment variables — which Vercel did not encrypt at rest by default — and accessed customer API keys, GitHub tokens, npm tokens, and source code. The incident highlights the danger of OAuth sprawl, especially as AI tools request broad permissions and employees adopt them without IT review. Vercel has shipped over 20 product improvements and recommends customers rotate all credentials stored in non-sensitive environment variables. The broader pattern mirrors previous breaches (Codecov, CircleCI, Snowflake, Okta) and points to a structural gap in how OAuth grants and non-human identities are governed.