T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Automatic Execution of an Unpinned npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23–24
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: HighVulnerable Code
json "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/poetry/mcp"]Technical Analysis
The Skill configuration invokes
npxwith the-yoption and requestsmcp-remote@latest. The-yoption suppresses installation confirmation, while the mutablelatesttag causes npm to retrieve and execute whichever package version is currently designated as the latest release.Consequently, the code executed when the MCP server starts is not fixed to the version that existed during security review. If the package, its npm publishing account, or one of its transitive dependencies is compromised, a later invocation can automatically download and execute attacker-controlled JavaScript. The downloaded package executes with the operating-system identity and effective permissions of the Agent process.
No evidence establishes that the current
mcp-remotepackage is malicious. The confirmed issue is the unsafe dependency retrieval and execution mechanism.Attack Path
- An attacker compromises the
mcp-remotenpm package, its publisher account, the relevant supply chain, or a transitive dependency. - The attacker publishes a malicious release and causes it to resolve through the
latesttag. - The Agent starts the configured
pipeworx-poetryMCP server. npx -yretrieves the newly designated package without requiring user confirmation.- npm executes the package under the Agent user's security context.
- The malicious package can access resources available to that process and may exfiltrate data, alter files, invoke local commands, or make unauthorized network requests.
Impact Assessment
Successful exploitation provides arbitrary code execution with the privileges of the user or service acco ...[truncated 606 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@x.y.z; do not use mutable npm tags or version ranges. - Install the dependency through a committed lockfile and use a deterministic installation command such as
npm ci. - Verify package integrity using lockfile integrity metadata, registry provenance, and an approved package hash where supported.
- Review the pinned package and its complete transitive dependency tree before deployment.
- Disable automatic installation during normal Skill startup. Prefer invoking a previously installed and verified local executable.
- Run the MCP client in a sandbox or container with a read-only filesystem where practical, minimal environment variables, no unnecessary credentials, and restricted outbound network access.
- Use automated dependency monitoring, but require security review before updating the pinned version.
- Replace
