In April 2026, Vercel experienced a security breach traced back to a compromised third-party AI tool called Context.ai, rather than a vulnerability in Vercel’s own infrastructure.
Incident Summary
- Disclosure Date: April 19, 2026.
- Root Cause: A supply chain attack targeting Context.ai, an AI productivity tool.
- Attack Vector: A Vercel employee granted “Allow All” OAuth permissions to Context.ai using their corporate Google Workspace account. Attackers, who had already compromised Context.ai, leveraged the stolen OAuth token to access the employee’s Vercel account and subsequently pivot into Vercel’s internal systems.
- Impact: Attackers gained access to internal environments and a limited subset of customers’ “non-sensitive” environment variables (e.g., API keys, database credentials). Sensitive environment variables, which are encrypted by default, were not compromised. No impact on Vercel’s core infrastructure, Next.js, or Turbopack.
- Extortion Attempt: Threat actor group “ShinyHunters” claimed responsibility and attempted to sell the stolen data for $2 million.
Recommendations for Users
- Rotate Secrets: Vercel advised all affected customers to rotate any environment variables not explicitly marked as “sensitive.”
- Audit OAuth Permissions: Review and revoke any unnecessary third-party OAuth integrations connected to Google Workspace or GitHub accounts.
- Utilize Sensitive Variables: Use Vercel’s “Sensitive Environment Variables” feature for all secrets, now made the default for new deployments.
- Monitor Activity: Monitor Vercel dashboards for suspicious activity or unauthorized deployments.
Vercel has engaged Mandiant and law enforcement for further investigation and has implemented enhanced security measures, including stricter defaults for environment variable security.