T08 · Insecure Dependencies
- Location
SKILL.md:43- Finding
Automatic Execution of an Unpinned npm Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 43–50
Vulnerability Type: Unpinned third-party dependency executed at runtime
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-crossref": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/crossref/mcp"] } } }Technical Analysis
The recommended MCP configuration invokes
npxwith both the automatic-confirmation option (-y) and the mutable package selectormcp-remote@latest. Consequently, the MCP client can download and execute whichever package release the npm registry identifies aslatestat invocation time.Because neither an exact audited version nor a package integrity hash is specified, the effective executable code can change after this Skill has been reviewed. A compromise of the npm package, its publisher account, or its dependency chain could therefore introduce arbitrary code into subsequent executions without requiring any modification to
SKILL.md.This finding does not establish that the current package is malicious. The vulnerability is the configuration's implicit trust in mutable, remotely retrieved executable code.
Attack Path
- A user copies the documented MCP configuration into a client.
- An attacker compromises the
mcp-remotenpm package, its publisher account, or a dependency used by a future release. - The attacker publishes a modified release and causes it to resolve through the
latesttag. - The MCP client starts the configured server and invokes
npx -y mcp-remote@latest. npxretrieves the attacker-controlled package without an interactive approval prompt.- npm package lifecycle logic or the package entry point executes with the privileges of the user running the MCP client.
Impact Assessment
Successful exploitation could execute arbitrary code under the MCP client user's account. Depe ...[truncated 371 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@X.Y.Z; do not use mutable tags or version ranges. - Install the dependency during a controlled deployment step rather than downloading and executing it automatically whenever the MCP server starts.
- Commit and enforce a lockfile containing integrity metadata, and verify the package and its transitive dependency hashes before installation.
- Review the package's source repository, publisher identity, release provenance, lifecycle scripts, and dependency tree before approving a version.
- Disable unnecessary npm lifecycle scripts where operationally possible.
- Run the MCP process in a restricted environment with minimal filesystem access, no unnecessary credentials, and constrained network permissions.
- Establish a deliberate update process in which new versions are security-reviewed and tested before the pinned version is changed.
- Replace
