T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Third-Party Packages Are Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 12–17
Vulnerability Type: Unverified and unpinned dependency installation
Risk Level: Highbash npm install @mnemopay/sdk claude mcp add -s user mnemopay -- npx -y @mnemopay/sdk mcpPython:
bash pip install mnemopayTechnical Analysis
The installation instructions retrieve npm and Python packages without pinning an exact reviewed version or verifying package integrity. In particular,
npx -y @mnemopay/sdk mcpautomatically approves package retrieval and executes the version resolved by the package registry at invocation time.The Claude command also creates a user-scoped MCP registration that refers to this mutable
npxpackage resolution. Consequently, a package version reviewed at one point in time may differ from the version executed during a later MCP launch. The project does not provide a lockfile, checksum, signature-verification procedure, or fixed local executable that would bind execution to a known artifact.This is a supply-chain weakness rather than evidence that the current MnemoPay packages are malicious. Exploitation would require compromise of the relevant package, publisher account, registry resolution, or transitive dependency.
Attack Path
- An attacker compromises the npm or Python publisher account, package distribution path, or a dependency used by the package.
- The attacker publishes a malicious release that remains compatible with the unpinned package name.
- A user follows the documented installation command, or Claude launches the user-scoped MCP registration through
npx. - The package manager resolves and downloads the attacker-controlled release without requiring an exact version or expected integrity value.
- Installation hooks or package runtime code execute with the privileges of the invoking user.
- The malicious code can access resources available to that user and may impersona ...[truncated 825 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin npm and Python dependencies to exact, security-reviewed versions rather than package names or floating ranges.
- Generate and retain lockfiles with integrity metadata, such as
package-lock.jsonfor npm and a hash-locked requirements file for Python. - Verify downloaded artifacts through registry integrity hashes, trusted signatures, or independently published checksums.
- Avoid registering an MCP command that uses unattended
npx -yresolution on every launch. Install a reviewed version once and register its fixed local executable path. - Disable install scripts where feasible, audit transitive dependencies, and scan package releases before deployment.
- Run the MCP service under a dedicated least-privileged account or sandbox with restricted filesystem, network, secret, and credential access.
- Continue exposing only the minimum necessary MCP tool groups, and require explicit authorization for administrative or operator capabilities.
- Document how users can remove or update the user-scoped MCP registration safely when a release is revoked or compromised.
