T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23-27
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
json { "mcpServers": { "pipeworx-lorem": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/lorem/mcp"] } } }Technical Analysis
The documented configuration invokes
npxwith the-yoption to download and executemcp-remote@latestwithout confirmation. Thelatesttag does not identify an immutable, reviewed package release. Consequently, the code executed by users can change after this Skill has been audited.This creates a supply-chain risk: compromise of the npm package, its publisher account, or its release process could cause a malicious future version to be selected and executed automatically. The project contains no lockfile, exact version constraint, or integrity hash capable of ensuring that users execute the same dependency that was originally reviewed.
The remotely hosted MCP endpoint also lies outside this repository and cannot be audited from the provided artifact. However, the reviewed file does not establish that the endpoint itself is malicious, so this finding is limited to the confirmed unsafe dependency invocation.
Attack Path
- An attacker compromises the
mcp-remotenpm package, its publishing credentials, or its release pipeline. - The attacker publishes a malicious package version and assigns or causes it to receive the
latesttag. - A user applies the documented MCP configuration.
npx -y mcp-remote@latestretrieves the attacker-controlled release without requesting confirmation.npxexecutes the malicious package in the local environment.- The payload operates with the permissions and accessible environment of the user or agent process that launched the MCP server.
Impact Assessment
Successful exploitation could result in arbitrary local code execution w ...[truncated 529 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, audited version such asmcp-remote@X.Y.Z. - Install the dependency through a package manifest and committed lockfile rather than downloading it dynamically on every invocation.
- Enforce package integrity verification using the package manager's lockfile integrity data or an equivalent cryptographic verification mechanism.
- Remove
-ywhere practical so unexpected downloads or package changes require explicit approval. - Review dependency provenance, publisher controls, release history, transitive dependencies, and published package contents before adoption.
- Use automated dependency monitoring, but require security review and testing before updating the pinned version.
- Run the MCP process in a restricted environment with minimal filesystem access, sanitized environment variables, limited network access, and no unnecessary credentials.
- Independently assess and constrain the remote MCP service because its server-side implementation is not included in this repository.
- Replace
