Vercel Published the OAuth App ID From Its Breach. Now Anyone Can Check If They Were Exposed.
For the first time in a major AI vendor breach, a company published the OAuth app ID, so admins can check if it reached their org. Vercel says only non-sensitive config values were taken. Whether they will actually run the check is the question left open.
Vercel has published the OAuth application ID from its breach linked to a Context.ai employee's infected laptop, enabling Google Workspace administrators to audit whether the same app accessed their organizations — an unprecedented level of transparency in AI vendor breach disclosure. The attack chain exploited a Vercel employee's use of their corporate account to sign up for a consumer AI product (AI Office Suite) with broad 'Allow All' Google permissions, which attackers leveraged to pivot into Vercel systems. While Vercel claims only non-sensitive environment variables were accessed and that encrypted secrets show no evidence of exfiltration, the same OAuth application may have affected hundreds of users beyond Vercel.
- •Publishing OAuth app IDs after a breach is a transparency practice that lets third-party organizations self-audit exposure, though most admins likely won't know to run this query.
- •The attack vector — a vendor employee's consumer-side tool sign-in using corporate credentials with permissive OAuth scopes — represents a supply chain risk that standard security controls often miss.
- •Lumma Stealer malware on a partner's endpoint provided initial access; organizations should extend threat modeling to include third-party access vectors, not just their own perimeter.
