Vercel April 2026 security incident

# Vercel April 2026 security incident | Vercel Knowledge Base Source: [https://vercel.com/kb/bulletin/vercel-april-2026-security-incident](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident) We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems\. We are actively investigating, and we have engaged incident response experts to help investigate and remediate\. We have notified law enforcement and will update this page as the investigation progresses\. In this bulletin: - [Updates](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#updates) - [Who is impacted](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#who-is-impacted) - [What we know](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#what-we-know) - [Recommendations](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#recommendations) - [Indicators of compromise \(IOCs\)](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#indicators-of-compromise-iocs) DateUpdateApril 19, 6:01 PM PSTWe published information about the[origin of the attack](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#what-we-know)and additional[Recommendations](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#recommendations)\.April 19, 11:04 AM PSTWe published an[IOC](https://vercel.com/kb/bulletin/vercel-april-2026-security-incident#indicators-of-compromise-iocs)to support the wider community in the investigation and vetting of potential malicious activity in their environments\. Initially we identified a limited subset of customers whose Vercel credentials were compromised\. We reached out to that subset and recommended an immediate rotation of credentials\. If you have not been contacted, we do not have reason to believe that your Vercel credentials or personal data have been compromised at this time\. We continue to investigate whether and what data was exfiltrated and we will contact customers if we discover further evidence of compromise\. We’ve deployed extensive protection measures and monitoring\. Our services remain operational\. The incident originated with a compromise of Context\.ai, a third\-party AI tool used by a Vercel employee\. The attacker used that access to take over the employee's Vercel Google Workspace account, which enabled them to gain access to some Vercel environments and environment variables that were not marked as “sensitive\.” Environment variables marked as "sensitive" in Vercel are stored in a manner that prevents them from being read, and we currently do not have evidence that those values were accessed\. We assess the attacker as highly sophisticated based on their operational velocity and detailed understanding of Vercel's systems\. We are working with Mandiant, additional cybersecurity firms, industry peers, and law enforcement\. We have also engaged Context\.ai directly to understand the full scope of the underlying compromise\. While we continue to take actions to protect Vercel systems and customers, here are best practices you should follow: - Review the activity logfor your account and environments for suspicious activity\. You can review activity logs[in the dashboard](https://vercel.com/activity-log)or via the[CLI](https://vercel.com/docs/cli/activity)\. - Review and rotate[environment variables](http://vercel.com/all-env-vars)\. If any of your environment variables contain secrets \(API keys, tokens, database credentials, signing keys\) that were not marked as sensitive, those values should be treated as potentially exposed and rotated as a priority\. - Take advantage of the[sensitive environment variables](https://vercel.com/docs/environment-variables/sensitive-environment-variables)feature going forward, so that secret values are protected from being read in the future\. - Investigate[recent deployments](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fdeployments)for unexpected or suspicious looking deployments\. If in doubt, delete any deployments in question\. - Ensure that[Deployment Protection](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fsettings%2Fdeployment-protection)is set to Standard at a minimum\. - Rotate your[Deployment Protection tokens](https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation), if set\. For help rotating your secrets or other technical support, contact us through[vercel\.com/help](http://vercel.com/help)\. Our investigation has revealed that the incident originated from a small, third\-party AI tool whose Google Workspace OAuth app was the subject of a broader compromise, potentially affecting its hundreds of users across many organizations\. We are publishing the following IOC to support the wider community in the investigation and vetting of potential malicious activity in their environments\. We recommend that Google Workspace Administrators and Google Account owners check for usage of this app immediately\. OAuth App:110671459871\-30f1spbu0hptbs60cb4vsmv79i7bbvqj\.apps\.googleusercontent\.com