Vercel has confirmed a security breach involving unauthorised access to certain internal systems, and the company says the incident affected a limited number of customer accounts and stored data.
The cloud platform provider disclosed that it is actively investigating the incident with help from outside incident response experts and has also notified law enforcement.
According to Vercel, the breach began with the compromise of Context.ai, a third-party AI tool used by one of its employees.
The attacker allegedly used that access to take over the employee’s Google Workspace account, which then gave them access to the employee’s Vercel account.
From there, the intruder moved deeper into Vercel’s environment and accessed systems used to enumerate and decrypt non-sensitive environment variables.
The company said its initial investigation found that a limited subset of customers had non-sensitive environment variables exposed.
These variables were described as values stored on Vercel that could be decrypted into plaintext, potentially exposing some credentials to the attacker. Vercel said it had directly contacted affected customers and urged them to rotate their credentials immediately.
As the investigation expanded, Vercel said it found a small number of additional accounts compromised in the same incident.
It also discovered another small group of customer accounts showing evidence of compromise that predated this attack and appeared unrelated, potentially linked to social engineering, malware, or other methods. Vercel said all affected customers in both groups have been notified.
The company described the threat actor as highly sophisticated, citing the speed of the operation and the attacker’s apparent knowledge of Vercel’s product API surface.
Vercel also said it is working with Google Mandiant, other cybersecurity firms, industry peers, and law enforcement as part of the response. Context.ai has also been engaged to help determine the wider scope of the original compromise.
Vercel said there is no evidence that the company’s npm packages were tampered with during the incident.
In coordination with GitHub, Microsoft, npm, and Socket, the company said it validated that its published packages were not compromised and that the software supply chain remains safe.
For customers, Vercel’s guidance is clear: enable multi-factor authentication, create passkeys or use an authenticator app, review activity logs, inspect recent deployments, and rotate any environment variables not marked as sensitive.
The company also warned that deleting a project or account is not enough to remove risk if exposed secrets still grant access to production systems.
As part of its response, Vercel said it is rolling out stronger protections for environment variables, improved security visibility, and enhanced activity log features.
Follow us on Google News, LinkedIn, and X to Get Instant Updates and Set GBH as a Preferred Source in Google.
