T08 · Insecure Dependencies
- Location
SKILL.md:50- Finding
Unpinned Third-Party Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 50–55
Vulnerability Type: Unpinned and automatically executed third-party dependency
Risk Level: Mediumjson { "mcpServers": { "pipeworx-countries": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/countries/mcp"] } } }Technical Analysis
The configuration invokes
npxwith both the-yoption and the mutable dependency specifiermcp-remote@latest. When the configuration is used,npxmay download the package version currently associated with the npmlatesttag and execute its code without interactive confirmation.Because
latestcan resolve to different package contents over time, the effective executable is not reproducible and can change after this Skill has been reviewed. If the npm package, its publisher account, or its release process is compromised, a malicious version could execute locally with the permissions of the user running the Agent.Attack Path
- An attacker compromises the
mcp-remotepackage, a maintainer account, or its publication pipeline. - The attacker publishes a malicious release and associates it with the mutable
latesttag. - A user installs or launches the documented MCP configuration.
npx -yresolves and downloads the malicious release without requesting confirmation.- Package lifecycle or runtime code executes with the Agent user's local privileges.
- The malicious code can access resources available to that user or manipulate communications between the Agent and the remote MCP endpoint.
Impact Assessment
Successful exploitation could result in arbitrary code execution under the account running the Agent. The accessible scope may include readable user files, environment variables, locally available credentials, and Agent or MCP configuration. The package could also alter or intercept MCP requests and respon ...[truncated 218 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@x.y.z. - Verify the selected package version and publisher before use.
- Install the dependency through a lockfile-controlled workflow and validate its registry integrity hash.
- Avoid
npx -yfor security-sensitive setup because it suppresses installation confirmation. - Prefer invoking a previously installed, reviewed local binary rather than downloading executable code at launch.
- Run the MCP bridge with least privilege in a restricted environment that limits filesystem, credential, and network access.
- Establish a controlled update process in which new dependency versions are reviewed and tested before the pinned version is changed.
- Replace
