T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned npm Dependency Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 22–24
Vulnerability Type: Unpinned executable third-party dependency
Risk Level: HighVulnerable Code
json "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/microlink/mcp"]Technical Analysis
The documented configuration invokes
npxwith the-yoption to download and executemcp-remote@latestautomatically. The mutablelatesttag does not identify a fixed, audited package version and provides no integrity constraint. Consequently, the code executed by users can change after this Skill has been reviewed without any corresponding modification to the repository.The
-yoption suppresses the normal installation confirmation, increasing the likelihood that a changed or compromised release will execute without user review. This creates a supply-chain trust boundary involving the npm registry, the package publisher, and the package's transitive dependencies.The configuration also passes an external MCP endpoint to the downloaded package. The remote service can change independently, but the repository provides no evidence that the endpoint itself is malicious; the confirmed vulnerability is the automatic execution of the unpinned npm dependency.
Attack Path
- An attacker compromises the npm publisher account, package release process, registry distribution path, or a relevant dependency.
- The attacker publishes a malicious version under the
latesttag ofmcp-remote. - A user applies the documented MCP configuration.
npx -yresolves the mutable tag, downloads the malicious release, and executes it without an interactive installation confirmation.- The malicious package runs with the permissions and environment available to the process that launched the Agent or MCP client.
- It may access files, environment variables, credentials, or network resources available to that account, subject to operating-system and sandbox ...[truncated 712 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an explicitly pinned and reviewed version, such asmcp-remote@x.y.z. - Verify the selected release and its transitive dependencies before deployment.
- Use lockfiles and npm integrity hashes where the surrounding installation mechanism supports them.
- Prefer a controlled installation step over automatic execution through
npx -y; removing-ycan at least preserve an interactive confirmation boundary. - Consider mirroring the approved package artifact in a trusted internal registry and restricting dependency retrieval to that source.
- Run the MCP process in a sandbox or dedicated low-privilege account with minimal filesystem, credential, and network access.
- Establish a deliberate update and re-audit process rather than following a mutable distribution tag.
- Document what information is transmitted to
https://gateway.pipeworx.io/microlink/mcpand restrict sensitive URLs or content from being submitted unless necessary.
- Replace
