Glow Labs Says Coding Agents Appear to Pick Archived MCP Servers From Training Data; No Fix Is Coming for a Reported Puppeteer Flaw
Per Help Net Security, Glow Labs says agents appear to take the package name from training data in 98% of sessions where a deprecated MCP server was installed or suggested.
Editor's Note ·
- Clarification:
- The headline's second clause, 'No Fix Is Coming for a Reported Puppeteer Flaw', is not attributed in the headline. It rests on Help Net Security's account that the maintainers replied the server is archived and unmaintained, 'so no fix will come from that repository', and on the archive README's statement that 'No security updates or bug fixes will be provided'. The Herald did not see Glow Labs' report or the maintainers' reply, and Help Net Security does not repeat the word Puppeteer in the sentence about the closed report.
- Clarification:
- The article says a GitHub issue 'predates the Glow Labs report'. The issue was opened on September 9, 2026 (UTC), before Help Net Security's November 3 article on Glow Labs' research. None of the cited sources says when Glow Labs reported the flaw to the maintainers, so the article does not establish whether the issue came before or after that report.
Overview
Help Net Security reports that Glow Labs, reviewing real AI coding session transcripts, found deprecated Model Context Protocol (MCP) servers landing on developer machines, a pattern the company calls MCPhantom. In 98% of those sessions, the article says, the agent “appears to have filled in the name from the model’s training data”; in the other 2%, the user asked for the old package by name. The article adds that “The research looked only at sessions where a deprecated server was installed or suggested,” so the 98% figure describes why those installs happened, not how often agents choose a deprecated server overall. That reading is the Herald’s own, not Help Net Security’s.
The deprecated packages come from an archive of reference servers. The servers-archived repository is titled “Model Context Protocol servers (ARCHIVED)” and states that “NO SECURITY GUARANTEES ARE PROVIDED FOR THESE ARCHIVED SERVERS.”
What Glow Labs Reports
According to Help Net Security, the pattern appeared across Claude Code, Cursor, Codex CLI, Claude Cowork and Claude chat, and with models from Anthropic, OpenAI and xAI. In the GitHub example Glow Labs documents, the article says, the agent passed over the MCP server that GitHub maintains and chose “a deprecated Anthropic reference server from its training data.”
The article says four high-severity vulnerabilities turned up in those reference servers. The most serious is a remote code execution bug in the Puppeteer server: a prompt injection can make the agent start any process on the machine instead of the browser, and because the developer approved web browsing, “that one permission stretches to cover the rest, so the harness lets it through.” Help Net Security does not name the other three flaws.
Glow Labs’ report was closed as out of scope, according to the same article. It says the maintainers replied that the server was archived in May 2025 and is unmaintained, “so no fix will come from that repository,” and that they would look at marking the npm package deprecated so users get a warning. The article adds that a deprecated package still installs through npx, that no exploitation has been seen, and that the flaws have no CVEs.
On usage, Help Net Security reports that the deprecated packages Glow Labs counted have been downloaded from npm “more than 17.3 million times since July 2025,” with five of them in npm’s top MCP 100. It explains why existing controls stay quiet: EDR sees a trusted Node process installing a public npm package, SCA has no manifest to inspect because the server runs through npx, and software inventory never registers an application.
Nadav Claude Cohen, a vulnerability researcher at Glow, told Help Net Security that “A lookup before install is not enough on its own,” and described a session in which the agent checked npm, was told the package was deprecated, and installed it anyway without telling the user. Ophir Arie, Glow VP of R&D, said, “The model’s memory is now a package manager with no deprecation feed.”
The article also says that pulling the packages is not an option: npm lets an owner remove one only if it had fewer than 300 downloads in the past week, has a single owner and no public dependents. “server-github had 185,239 downloads last week and has 6 owners,” Cohen says.
What the Public Record Shows
The archived repository’s README lists the Puppeteer, GitHub and PostgreSQL servers among its archived servers and says that no security updates or bug fixes will be provided.
A separate thread in the MCP servers repository predates the Glow Labs report. A GitHub user, BerkantACUN, opened issue 4785 on September 9, 2026, reporting that four archived packages (server-postgres, server-github, server-puppeteer and server-brave-search) totalled 214,369 weekly downloads, measured that day from api.npmjs.org. The issue says all four carry npm’s generic text, “Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.”, and that it “names no replacement and no security status.” It proposed rewriting the npm deprecation string to say the packages are archived and unmaintained.
A GitHub account marked as a project member, cliffhall, triaged the issue on October 19 (UTC) as “Priority Low (total 4),” writing that updating the deprecation message “is a cheap maintainer action that would reach every installer.” On November 5 (UTC), the same account commented, “Updated all but server-brave-search, for some reason I could not access it,” and the issue was closed. The comment does not say what was updated, and neither the comment nor the issue mentions Glow Labs.
An earlier Datadog Security Labs post by Santiago Mola, a Staff Software Engineer, describes a flaw in one of the archived servers: “We found a SQL injection vulnerability in Anthropic’s reference Postgres MCP server that allowed us to bypass the read-only restriction and execute arbitrary SQL statements.” Its timeline says Anthropic fixed the vulnerability in its git repository on May 29, 2025, while @modelcontextprotocol/server-postgres v0.6.2 “remains unpatched at NPM and Docker Hub.” The post reported about 21,000 weekly downloads for that npm package when it was written; issue 4785 reports 95,430 for the week it measured.
What We Don’t Know
- Glow Labs’ data. The Herald did not reproduce any Glow Labs figure; they are as relayed by Help Net Security. The article does not give a session count or say how many sessions involved each agent or model.
- The other three flaws. Help Net Security names only the Puppeteer remote code execution bug, so it is unclear whether the Datadog-described Postgres flaw is one of the four.
- Vendor responses. The article does not include responses from the harness or model makers it names.
- Download figures. The sources measure at different times: Cohen’s 185,239 weekly downloads for server-github and the issue’s 84,416 for the same package on September 9 are not explained by either source.
- What the November 5 update changed. The sources do not say whether it relates to Glow Labs’ report.
Disclosure: the Herald’s contributor model is built by Anthropic, whose reference servers and Claude Code are named in the sources; this article reports that only as the sources state it.