T08 · Insecure Dependencies
- Location
SKILL.md:40- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 40–46
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumThe documented MCP configuration invokes
npxwith automatic confirmation and the mutablelatestpackage tag:json { "mcpServers": { "pipeworx-dogsapi": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/dogsapi/mcp"] } } }Technical Analysis
The command uses
npx -yto download and executemcp-remote@latestwithout prompting the user and without pinning an audited version. Because thelatesttag can resolve to a different package release after the Skill has been reviewed, the code ultimately executed is not immutable.This creates a supply-chain exposure: compromise of the npm package, its publisher account, or its release process could cause a malicious future version to be downloaded and executed. The project contains no lockfile, integrity hash, or other mechanism that verifies the expected package artifact.
The documented
curlexample can call the fixed service endpoint directly, whereas the MCP configuration introduces a general-purpose third-party executable into the local environment.Attack Path
- An attacker compromises the
mcp-remotenpm package, its maintainer account, or its publishing pipeline. - The attacker publishes a malicious release and assigns it to the
latestdistribution tag. - A user enables or launches the documented MCP configuration.
npx -y mcp-remote@latestretrieves the attacker-controlled release without an interactive confirmation.- The downloaded package executes with the permissions and environment of the user or agent process.
- The malicious package can attempt to access resources available to that process or execute further commands.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the ...[truncated 636 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@X.Y.Z; do not use a mutable tag or version range. - Record and verify the expected package integrity hash through an appropriate lockfile or controlled installation process.
- Avoid
npx -yfor first-time or unverified execution so package installation does not proceed without user confirmation. - Prefer installing dependencies from a reviewed lockfile rather than downloading executable code dynamically whenever the Skill starts.
- Document the expected package publisher, version, and integrity value so users can validate the artifact.
- Run the MCP bridge in a restricted environment with only the filesystem, environment variables, and network access required for the dog-data service.
- Establish a controlled dependency-update process in which new versions are reviewed and tested before the pinned version is changed.
- Replace
