Vercel got breached. The hosting platform disclosed on April 19, 2026 that unauthorized actors accessed certain internal systems, and the incident has been attributed to ShinyHunters, a hacking group with a track record of corporate extortion through credential theft. Vercel says a limited subset of customers were impacted and they're reaching out directly. Services stayed online throughout.
The attackers didn't exploit a vulnerability in Vercel's edge runtime or application code. They got in by compromising legitimate internal credentials, likely through social engineering or infostealing malware, then used internal support and admin tooling to access customer project configurations. This was an IAM failure, full stop. No code vulnerability at all. Once authenticated, ShinyHunters hit an internal API endpoint designed for troubleshooting that let them enumerate and pull environment variables.
Vercel CTO Theo posted in Hacker News comments that environment variables marked as "sensitive" are safe. Everything else should be rotated. If you're running AI agents or applications on Vercel, check your environment variables now. The sensitive variable feature exists for exactly this scenario, and if you weren't using it, your secrets may have been exposed.
Your hosting provider's internal controls are part of your threat surface. Period. Vercel built a feature to protect credentials at rest inside their own infrastructure. That the feature existed but wasn't the default is the real story here.