T08 · Insecure Dependencies
- Location
SKILL.md:46- Finding
Unpinned Third-Party Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 46–49
Vulnerability Type: Unpinned npm dependency and automatic remote package execution
Risk Level: Mediumjson { "mcpServers": { "pipeworx-agify": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/agify/mcp"] } } }Technical Analysis
The MCP configuration invokes
npxwith the-yoption and referencesmcp-remote@latest. The-yoption suppresses installation confirmation, while the@latesttag dynamically resolves to whichever package release is current at execution time.Consequently, the code executed by this configuration is not fixed to the version reviewed during the audit. A future malicious or compromised release of
mcp-remote, compromise of its npm publishing account, or compromise elsewhere in the package distribution chain could cause arbitrary third-party code to run locally. The effective behavior can therefore change without any modification toSKILL.md.Attack Path
- An attacker compromises the npm package, its publisher account, or a dependency included in a future
mcp-remoterelease. - The malicious release becomes the version resolved by the
latestdistribution tag. - A user or MCP client loads the documented configuration.
- The client runs
npx -y mcp-remote@latest. npxdownloads the newly resolved package without requesting installation approval.- Package or lifecycle code executes with the privileges and environment of the user running the MCP client.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the MCP client's operating-system user account. Depending on that user's permissions and environment, malicious package code could read or modify accessible files, inspect environment variables and credentials, alter MCP communications, initiate network requests, or execute addi ...[truncated 303 chars]
- An attacker compromises the npm package, its publisher account, or a dependency included in a future
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an explicitly pinned and reviewed version, such asmcp-remote@x.y.z. - Remove
-ywhere interactive installation approval is practical. - Install dependencies through a controlled build or deployment process rather than downloading them dynamically whenever the MCP client starts.
- Use a lockfile and npm integrity hashes to ensure the resolved package and transitive dependencies match reviewed artifacts.
- Configure an approved package registry and apply package provenance or signature verification where supported.
- Scan the pinned package and its transitive dependencies before deployment.
- Establish a controlled update process in which new versions are reviewed and tested before the pinned version is changed.
- Run the MCP bridge with least privilege and restrict its access to sensitive files, credentials, and unnecessary network destinations.
- Replace
