As every week, our malware detection systems scan thousands of new and updated packages across public registries. We confirmed 2 malicious package versions between November 1 and 11, 2026, both on npm. Xygeni confirmed 1 of them.
An MCP Package in the List@ifasn/mmdd-doc-mcp, confirmed by Xygeni on November 4 at version 2.1.1, has a name that points to an MCP server, the kind of component AI coding agents install and run with the developer’s permissions. As agents add tools on their own, malicious packages are following them into the MCP ecosystem.
Also Confirmed@goparrot-dashboard/app on npm, at version 0.0.2, confirmed by the registry on November 2.
This snapshot is part of our ongoing Malicious Code Digest, where we validate new threats to help DevSecOps teams protect their pipelines before damage occurs.
The Full List: 2 Confirmed Malicious Package Versions
| Ecosystem | Package | Date |
|---|---|---|
| npm | @goparrot-dashboard/app:0.0.2 | November 2, 2026 |
| npm | @ifasn/mmdd-doc-mcp:2.1.1 | November 4, 2026 |
Two Packages, One Agent Angle: 2 Malicious Package Versions in Early November
A quieter start to the month, but not a harmless one. Both versions came from npm, and one of them, @ifasn/mmdd-doc-mcp, carries the name of an MCP server: the kind of tool AI coding agents add and run without a developer reviewing it first. Low volume doesn’t mean low risk when the target is the agent’s toolbox. Of the 2 versions, Xygeni confirmed 1.
Xygeni Malware Early Warning monitors npm, PyPI, Maven, Composer, OpenVSX, and other registries in real time, flagging threats at publication, before they reach a build. Xygeni’s Open Source Security platform adds the prioritization DevSecOps teams need to act on the ones that matter first.







