Vercel cybersecurity incidents and threat signals

Apr 19, 2026Infostealer

High

Vercel security incident via compromised Context.ai employee account

We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems. 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. Given the current progress of our investigation and remediation efforts, we are moving to an ad hoc cadence for Security Bulletin updates. We will continue to be transparent with our customers and the community. If there are critical updates, we will alert any affected customers and will update this Security Bulletin. We have provided a security bulletin subscription at the top of this page to make monitoring easier. Initially we identified a limited subset of customers whose non-sensitive environment variables stored on Vercel (those that decrypt to plaintext) were compromised. We reached out to that subset and recommended an immediate rotation of credentials. As part of our continued investigation into the April 2026 incident, we expanded our review to include additional IOCs and conducted a broader analysis of requests to the Vercel network and environment variable read events in our logs. That review led to two separate findings: First, we have identified a small number of additional accounts that were compromised as part of this incident, and we have notified the affected customers. Second, we have identified a small number of customer accounts with signs of compromise that appear to be separate from the April 2026 incident. Based on our investigation to date, these compromises do not appear to have originated on Vercel systems. We have already contacted those accounts and provided them with specific corrective actions to remediate potential risk. This activity does not appear to be a continuation or expansion of the April incident , nor does it appear to be evidence of an earlier Vercel security incident. 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 individual Vercel Google Workspace account, which enabled them to gain access to that employee’s Vercel account. From there, they were able to pivot into a Vercel environment, and subsequently maneuvered through systems to enumerate and decrypt non-sensitive environment variables. We assess the attacker as highly sophisticated based on their operational velocity and in-depth understanding of Vercel's product API surface. We are working with Google Mandiant, additional cybersecurity firms, industry peers, and law enforcement. We have also engaged Context.ai directly to understand the full scope of their compromise. In collaboration with GitHub, Microsoft, npm, and Socket, our security team has confirmed that no npm packages published by Vercel have been compromised. There is no evidence of tampering, and we believe the supply chain remains safe. While we continue to take actions to protect Vercel systems and customers, here are best practices you should follow: Add an additional layer of security by requiring at least two methods of authentication. Learn more in our 2FA documentation . Deleting your Vercel projects or account is not sufficient to eliminate risk. Compromised secrets may still provide access to production systems, so you must rotate them before deleting your projects or account. Review and rotate environment variables that were not marked as “sensitive.” Those values (API keys, tokens, database credentials, signing keys, etc.) should be treated as potentially exposed and rotated as a priority. Take advantage of the sensitive environment variables feature so that secret values are protected from being read in the future. Review the activity log for your account and environments for suspicious activity. You can review activity logs in the dashboard or via the CLI . Investigate recent deployments for unexpected or suspicious looking deployments. If in doubt, delete any deployments in question. Ensure that Deployment Protection is set to Standard at a minimum. Rotate your Deployment Protection tokens , if set. For help rotating your secrets or other technical support, contact us through 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 Vercel Reveals Preceding Customer Data Thefts in Ongoing Hack Probe Vercel uncovered evidence of hackers accessing a small number of customer accounts before the main April 2026 breach, possibly through social engineering or malware [2] [3] [5] . The primary incident stemmed from a Vercel employee's Google Workspace account compromise via third-party AI tool Context.ai [1] [2] [5] . Additional customer accounts were found compromised in the April event, with notifications sent to affected parties [2] [3] . CEO Guillermo Rauch stated hacker activity extended beyond the Context.ai breach, involving infostealer malware targeting tokens [2] . Vercel engaged incident response experts, notified law enforcement, and advised customers to rotate secrets [1] [5] . Vercel disclosed on April 23, 2026, that investigators found signs of prior unauthorized access to a small number of customer accounts before its main security incident earlier in the month. The company expanded its probe into the breach, which originated from a compromise at third-party AI tool Context.ai, and identified more affected accounts from the primary event. Vercel's update on its security incident page revealed a small number of customer accounts showed evidence of compromise independent of and predating the April incident, potentially due to social engineering, malware, or other methods [2] [3] [5] . The company reviewed network requests and environment variable read events in its logs to make this discovery. Context.ai confirmed its earlier breach, and both firms suggested potential wider impacts [2] . The stories that matter, in one email. Free — unsubscribe anytime.