T08 · Insecure Dependencies
- Location
SKILL.md:44- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 44-49
Vulnerability Type: Supply-chain risk caused by an unpinned executable dependency
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-gamedeals": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/gamedeals/mcp"] } } }Technical Analysis
The MCP configuration invokes
npxwith both the automatic-confirmation option (-y) and the mutable package versionmcp-remote@latest. When this configuration is used, npm can download and execute whichever package release thelatestdistribution tag references at that time.Because the executable dependency is not pinned to a reviewed version or integrity hash, its effective code can change after the Skill has been audited. Automatic confirmation further removes an opportunity for the user to inspect or reject the package before execution. This creates a third-party supply-chain exposure: compromise of the package, its maintainer account, or its publication pipeline could result in arbitrary attacker-controlled code being executed locally.
Attack Path
- An attacker compromises the
mcp-remotepackage, a maintainer account, or its release pipeline. - The attacker publishes a malicious release and causes the npm
latesttag to reference it. - A user applies the MCP configuration documented in
SKILL.md. npx -y mcp-remote@latestresolves and downloads the attacker-controlled release without interactive approval.- The malicious package executes with the privileges and environment of the user running the Agent or MCP client.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the Agent user's operating-system account. Depending on that account's permissions and environment, an attacker could access local files, environment variables, Agent-accessible credentials, and network resources; modify user-owne ...[truncated 294 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed package version, such asmcp-remote@X.Y.Z. - Remove
-ywhere practical so installation or execution requires explicit user confirmation. - Lock and verify dependency integrity using a lockfile and registry-provided integrity hashes, or vendor a reviewed copy of the client.
- Establish a controlled update process in which new versions are reviewed and tested before the pinned version is changed.
- Run the MCP client with least privilege in an isolated environment, exposing only the files, credentials, and network destinations required for game-deal queries.
- Restrict package installation to a trusted registry and monitor the selected package for ownership changes, unexpected releases, and security advisories.
- Replace
