MCPhantom: coding agents install MCP servers that will never be patched
In shortAgents recall MCP package names from their training data and install archived servers, some with known high-severity flaws.
What happened
Glow Security's research team reported that AI coding agents install deprecated MCP servers using package names recalled from training data, not from a live source. In the sessions where a deprecated server was installed, the agent supplied the package name in 98% of cases.
Most of the reference servers MCP launched with are now archived, and the archive says no security updates or bug fixes will be provided. Glow reported four high-severity vulnerabilities across them, including remote code execution in the Puppeteer server that a prompt injection can trigger. No CVE was assigned. The Cloud Security Alliance said it had no evidence of exploitation.
Why it worked
An agent's memory of a package name does not carry the package's status. In one session the agent checked npm, was told the package was deprecated, and installed it anyway.
What EndLayer shows or does
- Available now
Every MCP server declared on every device, with its transport, host and an MCP risk tier from what it can reach. An inventory of MCP configurations is where the Cloud Security Alliance's note says to start. Roadmap →
- Available now
Block a server once and it is removed from each tool's configuration after an administrator approves, including on laptops that were offline. Roadmap →
- Not covered
Knowing that a package is deprecated or archived. EndLayer does not read a registry's deprecation status.