Shai-Hulud Reaches the Official MCP Registry, Shipping Poisoned .claude and .vscode Settings
Shai-Hulud Reaches the Official MCP Registry, Shipping Poisoned .claude and .vscode Settings is a critical-severity supply chain compromise issue in MCP Registry entry "V.A.P.E" and five linked GitHub repositories, a MCP server. Affected: MCP Registry entry "V.A.P.E" and five linked GitHub repositories (npm outbreak: 440+ packages). It has been exploited in the wild.
Is MCP Registry entry "V.A.P.E" and five linked GitHub repositories running on your developers' machines? Anomity finds every device with this MCP server installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →
Key facts
- ID
shai-hulud-reaches-the-official-mcp-registry-shipping-poisoned-claude- Severity
- critical
- Attack type
- Supply chain compromise, Credential theft, Malware
- Component
- MCP Registry entry "V.A.P.E" and five linked GitHub repositories · MCP server
- Known exploited
- Yes
- Published
- Last verified
What is this vulnerability?
The worm behind this month's 440-package npm outbreak used the official Model Context Protocol Registry for the first time. A registry entry for a server called V.A.P.E, marketed as cryptocurrency security tooling, pointed at a clean PyPI package so automated scanning passed, while the linked GitHub repository carried the real payload as instructions inside .vscode/settings.json and .claude/settings.json. Opening or cloning the repository was enough to harvest developer tokens, cloud credentials and session keys. OX Security counted five active repositories distributing the poisoned agent settings and more than 3,800 public repositories still holding exfiltrated credential dumps.
Affected versions
| Affected | Fixed in |
|---|---|
MCP Registry entry "V.A.P.E" and five linked GitHub repositories (npm outbreak: 440+ packages) | No fixed version listed |
Am I affected by this vulnerability?
You are affected if you run MCP Registry entry "V.A.P.E" and five linked GitHub repositories (npm outbreak: 440+ packages).
How do I fix it?
Treat a registry listing as an unverified claim: this entry passed scanning precisely because the package it named was clean and the payload lived in the linked repository. Inventory every MCP server in the fleet against the registry entry it came from, and diff .claude/settings.json and .vscode/settings.json after any clone. Rotate developer tokens, cloud credentials and session keys on machines that opened an untrusted repository this month.
How do I find every machine running MCP Registry entry "V.A.P.E" and five linked GitHub repositories?
Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run MCP Registry entry "V.A.P.E" and five linked GitHub repositories and which version, then enforce a policy on it.