T08 · Insecure Dependencies
- Location
SKILL.md:43- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 43-49
Vulnerability Type:T08: Insecure Dependencies
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-breweries": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/breweries/mcp"] } } }Technical Analysis
The MCP configuration invokes
npxwith the-yoption and the mutable package referencemcp-remote@latest. This causes npm to download and execute whichever package release is tagged aslatestat invocation time, without interactive confirmation.Because neither an exact package version nor an integrity hash is specified, the code executed by this configuration can change after the Skill has been reviewed. If the package publisher, npm account, release pipeline, or package itself is compromised, an attacker could distribute malicious code through a new release. The
-yoption removes the installation confirmation that might otherwise alert the user to the download.Attack Path
- An attacker compromises the
mcp-remotepackage, its publisher account, or its release process. - The attacker publishes a malicious package version and assigns it the npm
latesttag. - A user installs or activates the documented MCP configuration.
npx -y mcp-remote@latestautomatically retrieves the attacker-controlled release.- npm executes the package locally with the privileges and environment of the user running the Agent.
- The malicious package can perform any operation permitted to that user, including reading accessible files, accessing inherited environment variables, making network requests, or modifying user-owned data.
Impact Assessment
Successful exploitation results in arbitrary local code execution with the privileges of the Agent process or operating-system user. The affected scope can include user-readable files, creden ...[truncated 294 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith a specifically reviewed, immutable package version. - Use a lockfile and npm integrity metadata to ensure the retrieved package matches the reviewed artifact.
- Remove
-ywhere practical so installation requires explicit user confirmation. - Verify the package publisher, repository, provenance attestations, and release-signing practices before deployment.
- Preinstall the reviewed dependency in a controlled build process rather than downloading executable code when the Skill is invoked.
- Run the MCP client with minimal filesystem, environment, and network permissions, preferably inside a sandbox or container.
- Establish a controlled update process in which new versions are reviewed and tested before changing the pinned version.
- Replace
