Vercel·Technology / SaaS·
Customer environment variables were exposed.
Vercel disclosed an OAuth-token supply-chain compromise involving access to internal systems and customer environment variables. The attached record does not establish the complete downstream scope.
Report freshness and timeline
- First publicly reported
- First disclosed
- Latest attached source
- Radar data checked
Coverage window — Dataset generated Aug 30, 2026, 12:03 UTC
Executive incident brief
- Incident confirmation
- Organization confirmed
- Mechanism
- Reported cause: Non-sensitive environment variables were not encrypted at rest
- Consequence
- Reported: Customer environment variables were exposed.
- Scope
- The complete extent is not established by this record.
1)Incident fact sheet
- Organization
- Vercel
- Industry
- Technology / SaaS
- Disclosed
- Entry path
- Third-party access
- Third party
- Context.ai
- Affected asset
- Vercel internal systems and customer project environment variables
- Country
- US
- Data involved
- Authentication tokens · Credentials · Business Confidential
- Reported impact
- Data exposure
- Attached evidence
- 10 independent domains · 10 sources
2)Evidence-backed incident path
- 01
Entry path
Initial access involved third-party access.
ConfidenceSecondaryExact excerpt
E1“the breach stemmed from the compromise of a third-party AI tool's Google Workspace OAuth application”
bleepingcomputer.com · Apr 19 - 02
Reported cause
Non-sensitive environment variables were not encrypted at rest
ConfidenceSecondaryExact excerpt
E2“not marked as sensitive and therefore not encrypted at rest”
bleepingcomputer.com · Apr 19 - 03
Third party
Context.ai
ConfidenceSecondaryExact excerpt
E3“naming Context.ai as the compromised third party”
trendmicro.com · Apr 20 - 04
Reached
Vercel internal systems and customer project environment variables
ConfidenceSecondaryExact excerpt
E4“access environment variables that were not marked as sensitive”
bleepingcomputer.com · Apr 19 - 05
Observed
Customer environment variables were exposed.
ConfidenceProbableExact excerpt
E5“exposing environment variables for an undisclosed but reportedly limited subset of customer projects”
trendmicro.com · Apr 20
3)Impact and scope ledger
Established
Supported at the stated evidence level.
Reported
Present in public reporting; not independently established by Radar.
Not publicly established
No qualifying public evidence in the attached record.
- The supplied record does not establish the full scope of exposed data
- That a Defence review would have prevented this incident
4)Relevance to your product
Third-party access can inherit more reach than the product team intended.
This pattern applies when…
- Products that authorize third-party OAuth applications to access customer environments.
Diagnostic questions
- Can an integration reach production secrets or customer data?
- Are scopes narrower than the vendor's full workspace access?
- Can tokens be isolated and revoked without breaking the product?
This incident does not establish your product's risk.
5)Sector context — Technology / SaaS
- 2 incident threads
- 1 incident threads
- 5 incident threads
- 2 incident threads
- 13 incident threads
- 5 incident threads
- 18 incident threads
- 16 incident threads
- 16 incident threads
- 16 incident threads
- 7 incident threads
- 29 incident threads
- Same incident family
- 56 Supply chain / third party
- Confirmed share
- 40% 52 confirmed · 78 reported
- Display family
- Supply chain Used for Radar's public chart taxonomy
Publicly disclosed incidents and reports from to . Historical discovery is partial and does not measure breach probability.
Explore Technology / SaaS in Radar →6)Defence control mapping
What Defence can test
Third-party integration review
- Can an integration reach production secrets or customer data?
- Are scopes narrower than the vendor's full workspace access?
- Can tokens be isolated and revoked without breaking the product?
What cannot be concluded
- This incident does not predict an individual product's risk.
- A mapped control does not establish that a Defence review would have prevented the event.
7)Public evidence ledger
10 attached sources across 10 independent domains. No attached source is marked as an organization or regulator primary source.
- E3, E5trendmicro.comThe Vercel Breach: OAuth Supply Chain Attack Exposes the Hidden Risk in Platform Environment Variables | Trend MicroOther public report · Apr 20 · CitedOther public reportCited
Exact excerpt
“environment variables for an undisclosed but reportedly limited subset of customer projects”
- E1, E2, E4bleepingcomputer.comVercel confirms breach as hackers claim to be selling stolen dataSpecialist reporting · Apr 19 · CitedSpecialist reportingCited
Exact excerpt
“not marked as sensitive and therefore not encrypted at rest”
- S3techcrunch.comVercel says some of its customers' data was stolen prior to its recent hack | TechCrunchEstablished press · Apr 23 · AttachedEstablished pressAttached
Exact excerpt
“The San Francisco-based app and website hosting company”
- S4cyberscoop.comVercel attack fallout expands to more customers and third-party systems | CyberScoopOther public report · Apr 23 · AttachedOther public reportAttached
Exact excerpt
“valuable tokens like keys to Vercel accounts”
Show all 10 sourcesShow the first six sources
Does this integration boundary exist in your product?
A bounded review can test the authorized web/API path without assuming this incident predicts your risk.