Vercel·Technology / SaaS·
Vercel third-party OAuth application opened a path to customer data.
Vercel said attackers reached internal systems through Context.ai, a third-party AI tool. Public reporting supports customer data access; the exact root cause and financial impact remain unestablished.
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
- Entry path: Third-party access
- Consequence
- Reported: Customer data was accessed.
- Scope
- The complete extent is not established.
1)Incident fact sheet
- Organization
- Vercel
- Industry
- Technology / SaaS
- Disclosed
- Entry path
- Third-party access
- Third party
- Context.ai
- Affected asset
- internal Vercel systems and environment variables
- Data involved
- Credentials · Authentication tokens
- Reported impact
- Data exposure
- Attached evidence
- 8 independent domains · 9 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
Third party
Context.ai
ConfidenceSecondaryExact excerpt
E2“The incident originated with a compromise of Context.ai, a third-party AI tool”
helpnetsecurity.com · Apr 20 - 03
Reached
internal Vercel systems and environment variables
ConfidenceSecondaryExact excerpt
E3“gain access to some of Vercel’s internal systems, including credentials that were not encrypted”
techcrunch.com · Apr 20 - 04
Observed
Customer data was accessed.
ConfidenceProbableExact excerpt
E4“accessed customer data”
techcrunch.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 exact technical root cause
- Whether any ransom or extortion payment was made
- 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 grant third-party OAuth applications access to cloud workspaces, credentials, or environment variables.
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
- 22 Data breach / intrusion
- Confirmed share
- 40% 52 confirmed · 78 reported
- Display family
- Data breach 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
9 attached sources across 8 independent domains. No attached source is marked as an organization or regulator primary source.
- E3, E4techcrunch.comApp host Vercel says it was hacked and customer data stolenEstablished press · Apr 20 · CitedEstablished pressCited
Exact excerpt
“customer credentials”
- E1bleepingcomputer.comVercel confirms breach as hackers claim to be selling stolen dataSpecialist reporting · Apr 19 · CitedSpecialist reportingCited
Exact excerpt
“the breach stemmed from the compromise of a third-party AI tool's Google Workspace OAuth application”
- E2helpnetsecurity.comVercel breached via compromised third-party AI tool - Help Net SecurityOther public report · Apr 20 · CitedOther public reportCited
Exact excerpt
“The incident originated with a compromise of Context.ai, a third-party AI tool”
Show all 9 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.