T08 · Insecure Dependencies
- Location
SKILL.md:50- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 50–56
Vulnerability Type: Unpinned executable dependency and supply-chain exposure
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-dadjokes": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/dadjokes/mcp"] } } }Technical Analysis
The setup invokes
npxwith both the automatic-confirmation option (-y) and the mutable dependency specifiermcp-remote@latest. Consequently, the command may download and execute whichever package release the npm registry identifies as the latest at installation or invocation time.The executed package is not constrained to the version that was available during this audit. Changes made by the package publisher, compromise of the publisher or npm account, or a malicious supply-chain release could therefore introduce arbitrary executable code after the Skill has already been reviewed.
No evidence establishes that the current
mcp-remotepackage is malicious. The vulnerability is the configuration's automatic execution of an unpinned, externally controlled dependency without a reviewed lockfile or integrity constraint.Attack Path
- An attacker compromises the dependency publisher, its npm account, its build or release pipeline, or another relevant supply-chain component.
- The attacker publishes a malicious version that becomes the release resolved by
mcp-remote@latest. - A user applies the documented MCP configuration and starts the configured server.
npx -ydownloads the attacker-controlled package without requesting interactive confirmation.- npm or
npxexecutes the package, including any applicable package lifecycle behavior, with the privileges and environment of the Agent user. - The malicious payload can access resources available to that user and perform arbitrary local actions.
Impact Assessment
Successful exploitation could prov ...[truncated 617 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith a reviewed, exact version, such asmcp-remote@x.y.z; do not uselatest, caret ranges, tilde ranges, or other mutable selectors. - Manage the dependency through a committed package manifest and lockfile rather than downloading it ad hoc for each invocation.
- Verify the resolved package using registry integrity metadata or a separately maintained cryptographic digest.
- Review the pinned package, its transitive dependencies, lifecycle scripts, and release provenance before deployment.
- Disable npm lifecycle scripts where operationally feasible, or install dependencies in a controlled build stage before runtime.
- Execute the MCP process under a dedicated, least-privileged account or sandbox with restricted filesystem, credential, environment-variable, and network access.
- Establish a controlled upgrade process in which dependency updates are reviewed, tested, and explicitly approved before changing the pinned version.
- Replace
