Vercel confirms breach via OAuth supply chain, hacker demands $2M ransom

Vercel confirmed a breach on April 19, 2026, tied to a third‑party OAuth compromise at Context.ai. The attacker demanded $2 million and posted alleged Vercel data on a hacking forum.

According to the report, the attacker accessed internal environments via a compromised Google Workspace OAuth app used by a Vercel employee. No direct bypass of Vercel auth is alleged. Source.

CEO Guillermo Rauch said customer environment variables are encrypted at rest. He added the attacker moved further through enumeration. A limited set of customers was told to rotate credentials. Source.

A forum post tied to “ShinyHunters” advertised internal data for $2 million. The post claims access keys, source code, database contents, NPM and GitHub tokens, and a file with about 580 employee records. Forum claim via X. Authentication of the dump is unverified. Ransom status is unknown. The attacker’s identity is unconfirmed. Source.

Vercel engaged Mandiant and law enforcement. It shared an Indicator of Compromise for the malicious OAuth app. Source.

Open‑source projects like Next.js and Turbopack are unaffected. Vercel added an environment variable overview page and improved sensitive variable controls in the dashboard. Source.

The article frames this as an OAuth supply‑chain risk across dev tooling, AI integrations, and deployment infra. It notes this vector sits outside smart contract audits and protocol‑level reviews. Source.

What’s allegedly in the leak:
- Access keys and internal deployment data Source
- Source code, database contents, NPM and GitHub API tokens Source
- Roughly 580 employee names, emails, and status records Source

Headline: Vercel confirms OAuth‑chain breach via Context.ai; $2M ransom claim, limited credential rotation underway