T08 · Insecure Dependencies
- Location
SKILL.md:55- Finding
Automatic Execution of an Unpinned npm Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 55–56
Vulnerability Type: T08: Insecure Dependencies
Risk Level: Mediumjson "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/deckofcards/mcp"]Technical Analysis
The MCP configuration invokes
npxwith the-yoption to automatically download and executemcp-remote@latest. Thelatestnpm tag is mutable and does not identify a fixed, previously audited package version. The configuration also provides no package integrity hash or lockfile protection.Consequently, the code executed by this configuration can change after the Skill has been reviewed. Automatic confirmation through
-yfurther removes an opportunity for the user to inspect or reject a newly resolved package version. This creates a supply-chain exposure if the package, its maintainer account, or its publication process is compromised.Attack Path
- An attacker compromises the
mcp-remotenpm package, a maintainer account, or the associated release process. - The attacker publishes a malicious package version and causes the mutable
latesttag to resolve to it. - A user starts the MCP server using the configuration in
SKILL.md. npx -ydownloads the version currently referenced bylatestwithout interactive confirmation.npxexecutes the malicious package locally.- The payload runs with the permissions and environmental access of the user or Agent process that launched the MCP server.
Impact Assessment
Successful exploitation could result in arbitrary code execution under the privileges of the launching user. Depending on that user's permissions and runtime environment, a malicious dependency could access readable local files, environment variables, credentials, Agent-accessible resources, and network services. It could also modify files or execute additional commands within the user's authorization boundary.
The reviewed evidence does not es ...[truncated 199 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version, such asmcp-remote@x.y.z. - Install dependencies during a controlled deployment step rather than downloading them automatically whenever the MCP server starts.
- Use a lockfile and npm integrity metadata to verify the resolved package artifact.
- Remove
-ywhere practical so unexpected installation or version-resolution changes require explicit approval. - Monitor the pinned dependency for security advisories and upgrade only after reviewing and testing the target version.
- Run the MCP bridge with least privilege in an isolated environment, exposing only the files, credentials, and network destinations required for its stated function.
- Replace
