T08 · Insecure Dependencies
- Location
SKILL.md:49- Finding
Unpinned Third-Party Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 49–55
Vulnerability Type: Supply-chain risk caused by automatic execution of an unpinned dependency
Risk Level: MediumVulnerable Code
json { "mcpServers": { "pipeworx-httpcat": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/httpcat/mcp"] } } }Technical Analysis
The documented MCP configuration invokes
npxwith the-yoption and the mutable package specifiermcp-remote@latest. This causes the current package release to be downloaded and executed automatically without an interactive confirmation step.Because
latestcan resolve to different package contents after the Skill has been reviewed, the effective code executed by this configuration is not stable or reproducible. No exact version, lockfile, or integrity digest is supplied. If the package, its publishing account, or an upstream dependency is compromised, a later invocation could execute attacker-controlled code under the privileges of the user or Agent process.The project contains only
SKILL.md; no embedded malicious script was identified. This finding concerns the unsafe dependency execution pattern rather than confirmed malicious behavior in the currently published package.Attack Path
- An attacker compromises the
mcp-remotepackage, its publisher account, or a dependency incorporated into a subsequent release. - The malicious release becomes the version resolved by the
latestdistribution tag. - A user applies the MCP configuration documented in
SKILL.md. npx -y mcp-remote@latestdownloads the newly resolved package without requesting confirmation.npxexecutes the package locally as the user or Agent running the MCP server.- The malicious package can perform actions permitted to that process, including accessing available files, environment variables, credentials, ...[truncated 563 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, audited package version, for examplemcp-remote@X.Y.Z. - Manage the dependency through a committed lockfile so that direct and transitive versions are reproducible.
- Verify package provenance and integrity using the package manager's integrity metadata, trusted registry controls, and available signature or provenance mechanisms.
- Avoid
npx -yfor first-time or dynamically resolved execution. Install the reviewed version through a controlled deployment process before launching it. - Run the MCP bridge with least privilege in a sandbox or container, exposing only the files, environment variables, and network destinations required for the HTTP-cat functionality.
- Establish a dependency-update review process that audits new versions before changing the pin.
- Replace
