Skip to content

AAK-SUPPLY-002: Known vulnerable package in lockfile

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

What it detects

A package with known MCP/AI-agent-related vulnerabilities was found in the dependency tree.

How to fix

Move the package named in the finding off the listed release, or remove it. The table 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. A 'Potential typosquat' finding is a name check: confirm the package is the one you meant to install, and replace it with the real package if it is not.

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

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

Limitations

Reads the root package-lock.json against a fixed table of the malicious axios releases of 31 March 2026 (1.14.1 and 0.30.4), every numeric release of plain-crypto-js, the trojan they install, and two misspellings of the MCP scope (@modlecontextprotocol, modelcontextprotocal). 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. A vulnerable version of any other package (lodash 4.17.15 in a lockfile) is not reported, and neither is any other lookalike name, such as an unscoped copy of an official server's (mcp-server-sequential-thinking for @modelcontextprotocol/server-sequential-thinking, which npm has since replaced with a security holding package). The rule used to report every mcp-server-<word>-<word> name, a shape real servers share. 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 table used to place it, is the empty placeholder 0.0.1. The table lists no PyPI package or crate (the PyPI openclaw is an unrelated installer for the cmdop CLI), so requirements*.txt, Pipfile.lock and Cargo.lock report nothing. yarn.lock, pnpm-lock.yaml, a package-lock.json in a sub-directory and a lockfile over 32 MiB are 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-002.md: the page then shows that text, with the registry reference appended under it.