Skip to main content
Mallory
← Back to News
third-party-vendor-breachidentity-authentication-vulnerabilitybreach-disclosure-notificationleaked-secret-api-key

Compromised Context.ai OAuth Access Led to Vercel Internal Breach

Breach & Incident Intelligence · 5 sources · Updated 5mo ago · First seen May 24, 2026

Compromised Context.ai OAuth Access Led to Vercel Internal Breach

Vercel disclosed that attackers accessed some internal systems after compromising Context.ai, an AI productivity tool used by a Vercel employee, and abusing broad Google Workspace OAuth permissions granted to the app. Using a valid OAuth token, the attacker reportedly took over the employee’s corporate account and pivoted through single sign-on into internal resources, including issue trackers, admin tools, and certain company environments. Vercel said some internal data and customer environment variables were exposed, including a limited number of customer credentials and API keys that had been classified as non-sensitive but were still usable.

The company notified affected customers and told them to rotate credentials while it investigated with Mandiant, other external firms, and law enforcement. Context.ai separately said a March intrusion into its AWS environment involved compromised OAuth tokens affecting some consumer users, linking that earlier breach to the later access into Vercel. Reporting also said the stolen Vercel data was offered for sale for $2 million by actors claiming ties to ShinyHunters, though known members denied involvement, and the incident has intensified scrutiny of SaaS integrations with excessive OAuth scopes and enterprise SSO access.

Is this vendor in your chain?See attribution, scope, and your downstream exposure.
Check the blast radius
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Apr 19, 2026 – Apr 20, 2026
  1. Apr 20, 20267mo ago

    Vercel discloses breach and notifies affected customers

    By April 20, 2026, Vercel disclosed that some internal systems had been accessed through the compromised third-party AI tool Context.ai and said a limited number of customer credentials were affected. The company notified impacted customers, advised them to rotate credentials, and said it was investigating with Mandiant, other external firms, and law enforcement.

  2. Apr 20, 20267mo ago

    Stolen Vercel data offered for sale for $2 million

    After the intrusion, stolen Vercel data was advertised for sale on the dark web for $2 million by a group claiming affiliation with ShinyHunters. Reported ShinyHunters members denied involvement.

  3. Apr 19, 20267mo ago

    Attacker uses compromised Context.ai access to infiltrate Vercel

    In April 2026, after a Vercel employee had authorized Context.ai with broad Google Workspace permissions, an attacker used a valid OAuth token to take over the employee's Google Workspace account and pivot via SSO into Vercel internal systems. The attacker accessed issue trackers, internal environments, admin tools, and environment variables, including some usable customer API keys that had been marked non-sensitive.

  4. Apr 19, 20267mo ago

    Context.ai suffers attack via compromised OAuth tokens

    In March 2026, Context.ai said an attack led to unauthorized access to its AWS environment through compromised OAuth tokens, affecting some consumer users. This compromise later became the foothold used in the Vercel incident.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Vercel

Organizations

2 linked
VercelContext.ai

Breaches

1 linked
VERCEL-2026-04
Do you run this?See attribution, scope, and whether this vendor sits anywhere in your supply chain.
Get the Full Incident Picture
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.