T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21-28
Vulnerability Type: Unpinned third-party package execution
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-jokes": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/jokes/mcp"] } } }Technical Analysis
The configuration invokes
npxwith the package specificationmcp-remote@latest. This causes the package manager to retrieve and execute whichever package release is associated with the mutablelatestdistribution tag at invocation time.The
-yoption suppresses the normal installation confirmation. Consequently, newly published package code can be executed automatically even if that version was never reviewed as part of this Skill. The configuration also provides no package integrity hash, lockfile, signature validation, or other mechanism for ensuring that the downloaded package is the expected audited artifact.This creates a supply-chain trust boundary: the effective executable code depends on the current state of the external package registry rather than solely on the reviewed project content.
Attack Path
- An attacker compromises the package maintainer account, package registry publication process, or another relevant supply-chain component.
- The attacker publishes a malicious version of
mcp-remoteand assigns it to thelatestdistribution tag. - A user installs or invokes this Skill using the documented configuration.
npx -yretrieves the attacker-controlled release without requesting user confirmation.- The malicious package executes with the privileges and environment of the user running the MCP server.
- Subject to operating-system or sandbox restrictions, the package could access user-readable files and environment variables, initiate network connections, alter user-owned files, or execute additional comm ...[truncated 716 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version, such asmcp-remote@x.y.z. Do not use mutable version tags or ranges. - Verify the selected release's provenance, maintainer identity, published contents, dependency tree, and known vulnerabilities before deployment.
- Use a local package manifest and lockfile so that direct and transitive dependency versions are reproducible.
- Enforce package integrity verification through lockfile integrity hashes, registry provenance attestations, or an approved internal package mirror.
- Avoid unattended
npx -yexecution. Install the verified package through a controlled deployment process and invoke the pinned local executable. - Run the MCP process in a restricted environment with minimal filesystem permissions, a sanitized environment, no unnecessary credentials, and outbound network access limited to required destinations.
- Establish a controlled update process in which new versions are reviewed and tested before the pinned version is changed.
- Replace
