T08 · Insecure Dependencies
- Location
SKILL.md:46- Finding
Unpinned Third-Party npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 46-54
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-dnd5e": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/dnd5e/mcp"] } } }Technical Analysis
The documented MCP configuration invokes
npxwith the mutable package specifiermcp-remote@latest. The-yoption suppresses interactive confirmation, allowing npm to download and execute whichever release is associated with thelatestdistribution tag at invocation time.Because the package version and integrity digest are not pinned, the effective executable payload can change after this skill has been reviewed. The project also provides no lockfile, vendored dependency, provenance verification, or checksum with which to validate the downloaded code.
This is a supply-chain exposure rather than evidence that the current
mcp-remotepackage is malicious. Exploitation would require compromise or malicious modification of the package, its publishing account, the npm distribution path, or a transitive dependency.Attack Path
- A user installs or copies the MCP configuration documented by the skill.
- The agent or MCP host launches the configured
npxcommand. - npm resolves the mutable
mcp-remote@latestpackage reference. - The
-yoption permits installation and execution without user confirmation. - An attacker who controls a future package release, publishing account, or relevant dependency introduces malicious code.
- The malicious package code executes locally under the account running the agent or MCP host.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the operating-system privileges of the user running
npx. Within those privileges, malicious package code could ac ...[truncated 496 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed package version rather than a mutable distribution tag. - Use a lockfile and integrity hashes to pin and verify all transitive dependencies.
- Review the selected package version and its dependency tree before deployment.
- Prefer a locally installed or vendored MCP client whose source and artifacts have been verified.
- Verify npm package provenance and signatures where supported.
- Avoid unattended first-time installation. Remove
-ywhere practical so unexpected package resolution requires explicit approval. - Run the MCP client in a sandbox or restricted service account with minimal filesystem, credential, environment-variable, and network access.
- Establish an explicit dependency-update process in which new versions are reviewed and tested before the pinned version is changed.
- Replace
