T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23-29
Vulnerability Type: T08: Insecure Dependencies
Risk Level: HighThe Skill configuration directs
npxto download and execute the mutablelatestrelease ofmcp-remotewithout version or integrity pinning:json { "mcpServers": { "pipeworx-npm": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/npm/mcp"] } } }Technical Analysis
The
@latestnpm tag is mutable and may resolve to different package contents each time the MCP server starts. The-yoption suppresses the interactive installation confirmation, causing the resolved package to be downloaded and executed automatically.This creates a supply-chain risk because the effective executable code is not fixed to the version reviewed during the audit. If the upstream package, maintainer account, publishing credentials, npm distribution channel, or mutable tag is compromised, a malicious release can be delivered to future users without any change to this Skill file.
Attack Path
- An attacker compromises the
mcp-remotepackage publication process or otherwise causes the npmlatesttag to reference a malicious release. - A user configures or launches the Skill using the documented MCP configuration.
npx -yresolvesmcp-remote@latest, downloads the attacker-controlled release, and suppresses installation confirmation.- The downloaded package executes locally under the account running the Agent.
- Malicious package lifecycle or runtime code performs actions available to that account.
Impact Assessment
Successful exploitation permits arbitrary code execution with the privileges of the user running the Agent or MCP server. Depending on that user's permissions, the malicious dependency could access readable local files and environment variables, modify user-owned data or configuration, make ...[truncated 279 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an explicitly reviewed, exact package version, such asmcp-remote@x.y.z. - Avoid automatic execution of dynamically resolved packages. Install the dependency through a controlled build or deployment process and invoke the installed binary.
- Commit and enforce a lockfile where applicable, and verify package integrity using npm integrity metadata or an equivalent cryptographic verification mechanism.
- Review package provenance, maintainers, release history, and published artifacts before approving version updates.
- Route dependency updates through automated security scanning and human review rather than tracking a mutable distribution tag.
- Run the MCP process in a least-privilege sandbox with restricted filesystem access, environment variables, process execution, and outbound network access to reduce the consequences of a compromised dependency.
- Replace
