T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 25-26
Vulnerability Type:T08: Insecure Dependencies
Risk Level: HighVulnerable Code
json "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/openalex/mcp"]Technical Analysis
The documented connection configuration invokes
npxwith both the-yoption and the mutable package specifiermcp-remote@latest. The-yoption suppresses installation confirmation, while@latestresolves to whichever package release is currently designated as latest by the npm registry.Consequently, the code executed by this Skill is not fixed to the version that existed when the Skill was reviewed. A future malicious release, compromised publisher account, or npm supply-chain incident could alter the effective executable payload without requiring any modification to
SKILL.md. No lockfile, exact version, package integrity hash, or controlled installation procedure is specified.Attack Path
- An attacker compromises the npm publisher account, package publication process, or another relevant supply-chain component for
mcp-remote. - The attacker publishes a malicious release and causes it to resolve through the
latesttag. - A user applies the documented MCP configuration.
npx -ydownloads the malicious release without requesting confirmation.- The downloaded package executes locally with the permissions of the user or Agent process.
- The malicious package can perform any operation available to that process, including reading accessible files, modifying user-owned data, executing child processes, or initiating outbound network connections.
Impact Assessment
Successful exploitation permits arbitrary local code execution within the security context of the process launching
npx. The attainable scope includes all files, environment variables, credentials, network resources, and subprocess capa ...[truncated 283 chars]- An attacker compromises the npm publisher account, package publication process, or another relevant supply-chain component for
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@X.Y.Z. - Install the dependency through a controlled build or deployment process rather than downloading and executing it dynamically with
npx -y. - Commit and enforce an npm lockfile where applicable.
- Verify package integrity through registry integrity metadata, cryptographic hashes, provenance attestations, and publisher verification.
- Run the connector in a sandbox or container with minimal filesystem, environment-variable, process, and network access.
- Establish a dependency update process that requires security review and testing before changing the pinned version.
- Monitor the dependency for ownership changes, unexpected releases, advisories, and registry compromise indicators.
- Replace
