Skip to content

AAK-SUPPLY-006: Dependency with known MCP-specific vulnerability

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/supply_chain.py
Auto-fixable
No.
SARIF name
McpSpecificVulnDep

What it detects

A dependency has a known vulnerability specifically affecting MCP/agent tooling.

How to fix

Change the package version in the server's args to a release the vulnerability database does not list, and pin it exactly. It lists releases published as malware: for axios 1.14.1 or 0.30.4 go back to 1.14.0 or 0.30.3, delete node_modules/plain-crypto-js, and rotate every secret on a machine that installed either release.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-SUPPLY-006

Limitations

Reads the args of the servers in the MCP configs AAK-SUPPLY-001 reads at the project root (.mcp.json, .cursor/mcp.json, .vscode/mcp.json, .amazonq/mcp.json and mcp.json), under mcpServers or VS Code's servers, and looks each package@version up in the npm section of the vulnerability database, which bundles the malicious axios releases of 31 March 2026 (1.14.1 and 0.30.4) and every numeric release of plain-crypto-js, the trojan they install; a copy aak update cached at ~/.agent-audit-kit/vuln_db.json wins over the bundled one. Every other malicious release is AAK-MALICIOUS-RELEASE-001's, and where that rule reports the same release in the same file this finding stands down. OpenClaw is not in it: it publishes calendar versions, which its own CVE pins read, and the only openclaw below 2.1.0, where the database used to place it, is the empty placeholder 0.0.1. The same package in package.json, in claude_desktop_config.json or in a sub-project's .mcp.json is not reported, and neither is a package that states no version. An MCP config over 1 MB is not read.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-SUPPLY-006.md: the page then shows that text, with the registry reference appended under it.