T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 25-26
Vulnerability Type: Supply-chain risk through an unpinned executable dependency
Risk Level: MediumVulnerable Code
json { "mcpServers": { "pipeworx-nvd": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/nvd/mcp"] } } }Technical Analysis
The configuration invokes
npxwith the-yoption to download and executemcp-remote@latestwithout interactive confirmation. The@latesttag is mutable and does not identify the exact package version that was reviewed. Consequently, the code executed on a future installation can differ from the code available at audit time.If the npm package, its maintainer account, publication pipeline, or one of its transitive dependencies is compromised, an attacker could publish malicious code under a version selected by
@latest. Package installation lifecycle scripts or the package executable could then run attacker-controlled code locally.Attack Path
- An attacker compromises the
mcp-remotepackage publication process, a maintainer account, or a relevant dependency. - The attacker publishes a malicious release that becomes the package version resolved by the
latesttag. - A user enables the documented MCP configuration.
npx -yretrieves the current package version without requesting confirmation.- npm lifecycle code or the downloaded package executable runs with the privileges of the user operating the agent.
- The malicious process can access resources available to that user and may establish outbound communications or modify user-accessible files.
This path is conditional on a package or supply-chain compromise; the audited file does not itself contain a confirmed malicious payload.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the acc ...[truncated 412 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith a specifically reviewed, immutable version, such asmcp-remote@x.y.z. - Record and verify package integrity using a lockfile, npm integrity metadata, or a trusted internal package mirror.
- Review the pinned package, its lifecycle scripts, and its complete transitive dependency tree before deployment.
- Disable or restrict npm lifecycle scripts where operationally possible.
- Execute the MCP process in a sandbox or container with minimal filesystem access, restricted environment variables, no administrative privileges, and tightly controlled outbound networking.
- Establish a controlled dependency-update process in which new versions are reviewed and tested before the pinned version is changed.
- Replace
