Was your project affected by the
Vercel April 2026 incident?
Attackers compromised a third-party AI integration and used it to silently exfiltrate Vercel deployment tokens across hundreds of projects. Run the four checks below to see if your project is exposed to the same attack patterns.
Tokens are used for a single API request and never stored or logged. GitHub checks use only the public API.
Scans your public repo's .github/workflows/ for AI-named GitHub Actions referenced by mutable tags instead of commit SHAs — the exact vector used to compromise pipelines in April 2026.
Checks your installed integrations for dangerous scope combinations (env:read + deployments:write) and scans your audit log for suspicious activity between March 28 – April 12, 2026 — the confirmed incident window.
Note: Integration flagging is scope-based — any integration holding env:read, deployments:write, or secrets:read is flagged as a risk, regardless of vendor. Vercel has not published a list of confirmed-compromised integration names.
Paste your .mcp.json, hermes.json, or any agent config. We run the same patterns as AgenticSupplyChainAgent to detect credentials being forwarded to third-party tool servers — the silent exfiltration channel at the core of the April 2026 attack.
Spread the word
Know someone on Vercel?
Forward this checker to teammates or coworkers who use Vercel. The checks take 2 minutes and require no account.
What each check detects
Finds GitHub Actions with AI-related names (copilot, claude, openai, devin, cursor…) that are referenced by mutable tags like @v2 instead of a full 40-character commit SHA. A tag-repointing attack can silently replace any of these with a credential stealer.
Lists your Vercel integrations and flags any that hold env:read, env:write, deployments:write, or secrets:read scopes. These are the scopes that gave the April 2026 attack access to deployment tokens without triggering any anomaly alerts.
Pulls your Vercel audit log and looks for environment variable reads, unexpected deployments, and new token creations that occurred between March 28 and April 12 — the confirmed incident window from the Vercel security bulletin.
Runs the same patterns as AgenticSupplyChainAgent on your pasted MCP or Hermes config to detect high-value credentials (VERCEL_TOKEN, GITHUB_TOKEN, API keys) being forwarded to non-localhost tool servers — a silent ongoing exfiltration channel.
Based on the Vercel April 2026 Security Bulletin and our full incident analysis. Detection powered by AgenticSupplyChainAgent — open source, MIT licensed.