Vercel Security Breach — What Happened and What You Should Do

Vercel confirmed a breach involving customer data through a third-party AI tool. Here is the breakdown and recovery steps.

Cloud hosting giant Vercel confirmed this weekend that hackers breached its internal systems and accessed customer data — through a compromised third-party AI tool. Here’s everything you need to know and the steps you should take right now.

What Happened

The Attack

A Vercel employee installed Context AI’s Office Suite app and connected it to their corporate Google Workspace account via OAuth.
A Context AI employee had been infected with Lumma infostealer malware in February 2026 (traced back to downloading Roblox “auto-farm” scripts).
That infection exposed Context AI’s credentials, including their Google OAuth tokens.
Hackers used the OAuth connection to take over the Vercel employee’s Google Workspace account.
From there, they pivoted into Vercel’s internal environments and accessed unencrypted environment variables.

What Was Stolen

Customer API keys and environment variables (non-sensitive ones).
Internal deployment credentials.
580 Vercel employee records — names, email addresses, account status, and activity timestamps.
Possibly source code and database data (claimed by the threat actor, unverified).

Who’s Selling the Data

A threat actor claiming to be ShinyHunters posted on BreachForums advertising the stolen data for $2 million, including API keys, source code, and access to internal deployments. The actual ShinyHunters group has denied involvement.

What Is NOT Affected

Feature	Status
Next.js	✅ Not affected
Turbopack	✅ Not affected
Sensitive environment variables	✅ Encrypted at rest, no evidence of access
On-chain crypto protocols (e.g. Orca)	✅ Not affected

Timeline

Date	Event
February 2026	Context AI employee infected with Lumma infostealer
March 2026	Context AI identifies and blocks unauthorized access to its AWS environment
April 17–19, 2026	Hackers pivot into Vercel’s internal systems via OAuth
April 19, 2026	Vercel publicly discloses the breach
April 20, 2026	Hudson Rock links breach to the February infostealer infection

Instructions for Vercel Users

1. Rotate your credentials

Immediately rotate all API keys, tokens, and secrets stored as environment variables in your Vercel projects — treat every non-sensitive variable as potentially compromised.

2. Audit your access logs

Review your Vercel project logs and Google Workspace audit logs for the window of April 17–19, 2026 for any suspicious access or changes.

3. Check your Google Workspace for the malicious OAuth app

Go to Google Admin Console → Security → API Controls → Manage Third-Party App Access and search for this OAuth Client ID: 110671459871-30f1spbu0hptbs60cb4vsmv79i7bbvqj.apps.googleusercontent.com

If it appears, revoke access immediately.

4. Mark sensitive variables as “Sensitive”

In your Vercel dashboard, go to your project’s Environment Variables settings and enable the Sensitive flag on any variable containing secrets. Sensitive variables are encrypted at rest and cannot be read back.

Incident Summary

Metric	Detail
Disclosed	April 19, 2026
Attack vector	OAuth supply chain via Context AI
Root cause	Lumma infostealer on a Context AI employee’s machine
Data exposed	Employee records, API keys, env variables
Asking price	$2 million
Next.js Affected	No