🔓 What Happened

Vercel — the cloud platform behind Next.js, used by millions of developers worldwide — has confirmed a security breach involving unauthorized access to internal systems. The disclosure came on April 19, 2026, via an official security bulletin.

Simultaneously, a threat actor using the “ShinyHunters” moniker posted on BreachForums claiming to sell Vercel’s internal database, access keys, source code, and API tokens for $2 million. The listing references Next.js and Turborepo and suggests the data could enable a large-scale supply chain attack.

However, CyberInsider reports that Vercel is not currently listed on ShinyHunters’ known extortion portal, and the group denied involvement when contacted — suggesting this may be a copycat actor operating under the same name.

🕵️ How the Breach Happened

Vercel’s security bulletin reveals the attack vector: a third-party AI tool whose Google Workspace OAuth app was compromised. The OAuth app ID has been published as an indicator of compromise:

OAuth App: 110671459871-30f1spbu0hptbs60cb4vsmv79i7bbvqj.apps.googleusercontent.com

This is significant. The breach didn’t come through Vercel’s own infrastructure — it came through a small third-party AI tool that had Google Workspace OAuth access. Once that tool was compromised, attackers gained access to hundreds of organizations that had authorised the app, including Vercel’s internal systems.

It’s a supply chain attack on a supply chain company. The same pattern we’ve seen with SolarWinds, CrowdStrike, and now — through a Google Workspace OAuth app — Vercel.

💣 What’s at Risk

According to the BreachForums listing and Vercel’s own advisory:

• Environment variables not marked as “sensitive” may be exposed — including API keys, database credentials, and signing keys
• Source code for internal Vercel systems
• Access keys and deployment tokens tied to Vercel’s infrastructure
• NPM tokens and GitHub tokens — potentially giving attackers push access to packages with 6 million weekly downloads (Next.js)
• Database information from Vercel’s internal systems

The supply chain implications are enormous. If attackers gained access to Next.js’s deployment pipeline, a single malicious commit could affect millions of applications worldwide. Vercel owns Next.js, and the framework has become the default React framework for enterprise applications.

🛡️ What Vercel Is Saying

Vercel’s official statement is measured:

“We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems, impacting a limited subset of customers.”

The company says:

• External incident response experts have been engaged
• Law enforcement has been notified
• Only a “limited subset” of customers are impacted and being contacted directly
• Services remain operational
• Environment variables marked as “sensitive” are stored in a way that prevents them from being read — and Vercel says it has “no evidence” those were accessed

But “no evidence of access” is not the same as “confirmed not accessed.” The investigation is ongoing.

⚡ What Every Developer Should Do Right Now

If you use Vercel — or any platform connected to it — take these steps immediately:

1. Rotate all environment variables — especially any API keys, database credentials, signing keys, and tokens that were not marked as “sensitive” in Vercel’s dashboard
2. Review your activity logs — check Vercel’s activity log in the dashboard or via the CLI for any suspicious deployments or configuration changes
3. Check for the compromised OAuth app — Google Workspace admins should search for app ID 110671459871-30f1spbu0hptbs60cb4vsmv79i7bbvqj.apps.googleusercontent.com in their organisation’s authorised apps and revoke access immediately
4. Mark environment variables as “sensitive” going forward — Vercel’s sensitive variable feature encrypts values and prevents them from being read, even by internal systems
5. Audit your supply chain — if you depend on Next.js packages, verify integrity and monitor for unexpected updates
6. Enable 2FA on all connected accounts (GitHub, NPM, Google Workspace)

🌐 The Bigger Picture

This breach highlights a vulnerability that goes far beyond Vercel: third-party OAuth apps are a massive attack surface. When you authorise a small AI tool to access your Google Workspace, you’re trusting that tool’s security practices. If that tool is compromised, every organisation that authorised it becomes vulnerable.

The attack vector — a compromised third-party AI tool — is particularly ironic given Vercel’s positioning as an “Agentic Infrastructure” platform. The company’s own bio reads “Agentic Infrastructure for apps and agents.” The very ecosystem Vercel is building for was the vector used to breach it.

For New Zealand developers and startups using Vercel (and many do — it’s the default for Next.js deployments), this is a wake-up call. Rotate your credentials, audit your OAuth apps, and treat every third-party integration as a potential attack surface.

---

🔍 THE BOTTOM LINE: Vercel was breached through a compromised third-party AI tool’s Google Workspace OAuth — not through their own code. But the impact could be massive: NPM tokens, GitHub access, and deployment keys may be in the hands of attackers selling access for $2M. If you use Vercel, rotate your credentials now. If you authorise third-party apps to access your Google Workspace, audit them today. Supply chain attacks are the new normal — and this one hit the infrastructure millions of developers depend on.

Sources: Vercel Security Bulletin, CyberInsider, XDA Developers