T08 · Insecure Dependencies
- Location
SKILL.md:51- Finding
Automatic Execution of an Unpinned npm Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 51–53
Vulnerability Type: Unpinned and automatically executed third-party dependency
Risk Level: Highjson "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/geo/mcp"] }Technical Analysis
The MCP configuration invokes
npxwith the-yoption to download and executemcp-remote@latestautomatically. Thelatesttag is mutable, so the package code executed at installation time can differ from the version available when the skill was reviewed.Because
npxexecutes the downloaded package locally, a compromised npm package, maintainer account, publishing pipeline, or future malicious release could result in arbitrary code execution. The-yoption removes the interactive confirmation that might otherwise alert the user to package installation.This is an insecure supply-chain configuration because neither an exact package version nor an integrity digest is specified. The effective executable payload is therefore outside the reviewed project and can change without any modification to
SKILL.md.Attack Path
- An attacker compromises the
mcp-remotenpm package, its maintainer account, or its release pipeline. - The attacker publishes a malicious release and assigns it to the
latestdistribution tag. - A user enables the documented MCP configuration.
npx -yretrieves the attacker-controlled package without requesting confirmation.- The package executes locally with the privileges of the user or agent process.
- The malicious package can access data and perform operations available to that process.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the permissions of the account running the MCP server. Depending on the execution environment, this may expose readable files, environment variables, agent-accessible credentials, network resources, ...[truncated 417 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@x.y.z. - Install the dependency through a committed package manifest and lockfile that records the resolved package and integrity hash.
- Remove
-ywhere interactive installation is appropriate so unexpected downloads require explicit approval. - Configure npm to use a trusted registry and enforce lockfile integrity during installation.
- Review the selected package version and its transitive dependencies before deployment.
- Run the MCP process in a sandbox or container with minimal filesystem, credential, and network access.
- Use automated dependency monitoring, but require review and testing before updating the pinned version.
- Where practical, install an internally mirrored and verified package artifact rather than retrieving executable code dynamically at startup.
- Replace
