T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26-27
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: Mediumjson "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/pokemon/mcp"]Technical Analysis
The documented configuration invokes
npxwith both the automatic-confirmation option (-y) and the mutablemcp-remote@latestversion selector. Consequently, following the instructions can download and execute whichever package release the npm registry currently assigns to thelatesttag.Because neither an exact version nor an integrity digest is specified, the code executed by users may differ from the code that was available when this skill was reviewed. Compromise of the package, its publisher account, or its release process could therefore turn this dependency-installation command into an arbitrary code-execution channel. The reviewed file does not establish that the current package is malicious; the vulnerability is the unsafe, mutable supply-chain trust model.
Attack Path
- An attacker compromises the
mcp-remotenpm package, its publisher credentials, or its release pipeline. - The attacker publishes a malicious release and assigns it to the npm
latestdistribution tag. - A user follows the skill documentation and starts the configured MCP server.
npx -yretrieves the attacker-controlled release without an interactive package-installation confirmation.- The malicious package executes locally with the permissions and environment available to the user who launched the MCP server.
- It may then access user-readable information, modify user-writable resources, or intercept MCP requests and responses.
Impact Assessment
Successful exploitation permits arbitrary code execution under the invoking user's account. The accessible scope can include files, environment variables, credentials, network resources, ...[truncated 325 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith a reviewed, exact package version; do not use a mutable distribution tag. - Manage the dependency through a committed lockfile and require integrity verification for the resolved package.
- Remove automatic confirmation where practical so unexpected installation or resolution changes are visible to the operator.
- Verify and document the expected package publisher, source repository, release provenance, and package signature or attestation.
- Review dependency updates before deployment and use automated supply-chain scanning to detect compromised, deprecated, or unexpectedly changed releases.
- Run the MCP process in a least-privilege sandbox with restricted filesystem, environment-variable, credential, and network access to limit the impact of a compromised dependency.
- Replace
