Here's my update to the broader community about the ongoing incident investigation. I want to give you the rundown of the situation directly. A Vercel employee got compromised via the breach of an AI platform customer called https://t.co/7PY6gGtzgI that he was using. The details are being fully investigated. Through a series of maneuvers that escalated from our colleague’s compromised Vercel Google Workspace account, the attacker got further access to Vercel environments. Vercel stores all customer environment variables fully encrypted at rest. We have numerous defense-in-depth mechanisms to protect core systems and customer data. We do have a capability however to designate environment variables as “non-sensitive”. Unfortunately, the attacker got further access through their enumeration. We believe the attacking group to be highly sophisticated and, I strongly suspect, significantly accelerated by AI. They moved with surprising velocity and in-depth understanding of Vercel. At the moment, we believe the number of customers with security impact to be quite limited. We’ve reached out with utmost priority to the ones we have concerns about. All of our focus right now is on investigation, communication to customers, enhancement of security measures, and sanitization of our environments. We’ve deployed extensive protection measures and monitoring. We’ve analyzed our supply chain, ensuring Next.js, Turbopack, and our many open source projects remain safe for our community. The recommendation for all Vercel customers is to follow the Security Bulletin closely (https://t.co/BLVnic9fJC). My advice to everyone is to follow the best practices of security response: secret rotation, monitoring access to your Vercel environments and linked services, and ensuring the proper use of the sensitive env variables feature. In response to this, and to aid in the improvement of all of our customers’ security postures, we’ve already rolled out new capabilities in the dashboard, including an overview page of environment variables, and a better user interface for sensitive env var creation and management. As always, I’m totally open to your feedback. We’re working with elite cybersecurity firms, industry peers, and law enforcement. We’ve reached out to Context to assist in understanding the full scale of the incident, in an effort to protect other organizations and the broader internet. I also want to thank the Google Mandiant team for their active engagement and assistance. It’s my mission to turn this attack into the most formidable security response imaginable. It’s always been a top priority for me. Vercel employs some of the most dedicated security researchers and security-minded engineers in the world. I commit to keeping you updated and rolling out extensive improvements and defenses so you, our customers and community, can have the peace of mind that Vercel always has your back.
Vercel Discloses Security Breach Triggered by Compromised Third Party AI Tool
· Updated
Vercel, a cloud platform for frontend developers, disclosed a security incident originating from a compromise of Context.ai, a third-party AI tool used by an employee. The attacker leveraged a breached
OAuth app to take over the employee's Google Workspace account and access internal environments.This incident marks a shift toward AI-accelerated threats, with the attacker moving with unusual velocity. While Vercel has recently focused on anti-fragile infrastructure and agent-driven terminal automation, this breach demonstrates how third-party AI tools can bypass infrastructure-level protections through standard employee permissions.
You should immediately rotate any environment variables on Vercel not marked as "sensitive." This security response follows the release of observability tools for generative interfaces, as Vercel rolls out new dashboard capabilities that default all new variables to "sensitive" and improve team-wide management.
Guillermo Rauch
@rauchg
910retweets6.2klikes
View on XStill wondering? A few quick answers below.
The incident began when an attacker compromised Context.ai, a third-party AI platform used by a Vercel employee. By breaching the tool's Google Workspace OAuth app, the attacker gained control of the employee's account and escalated access into internal Vercel environments to enumerate and exfiltrate data.
Non-sensitive environment variables are stored in a way that allows them to be decrypted into plaintext, making them vulnerable if an attacker gains internal access. Sensitive environment variables use enhanced encryption that prevents them from being read even by authorized internal systems. Vercel now defaults all new environment variables to the sensitive setting.
Vercel believes the attacking group was significantly accelerated by AI, allowing them to move with surprising velocity. The attackers demonstrated a sophisticated and in-depth understanding of Vercel's internal systems, using AI to navigate the environment and escalate their access more quickly than traditional manual methods would typically allow.
No, Vercel confirmed that its open-source supply chain remains secure. After an investigation with partners like GitHub and npm, the security team found no evidence of tampering with Next.js, Turbopack, or any other published npm packages. The breach was limited to internal systems and specific customer environment variables.
Users should immediately rotate any environment variables that were not marked as sensitive, such as API keys and database credentials. It is also recommended to enable multi-factor authentication, review account activity logs for suspicious behavior, and ensure that all future secrets use the sensitive environment variable feature to prevent unauthorized reading.





