T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Third-Party Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21–27
Vulnerability Type: Unpinned dependency execution throughnpx
Risk Level: Mediumjson { "mcpServers": { "pipeworx-jikan": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/jikan/mcp"] } } }Technical Analysis
The configuration invokes
npx -yto download and executemcp-remote@latest. Thelatestnpm tag is mutable and does not identify an immutable, previously reviewed release. The-yoption suppresses confirmation, allowing the resolved package and its dependency tree to execute automatically.The project contains no exact version pin, package lockfile, integrity hash, or local implementation that would constrain the package to audited content. Consequently, the effective code executed by this skill can change after the skill itself has been reviewed.
This finding does not establish that the current
mcp-remotepackage is malicious. It identifies a supply-chain execution path that could become exploitable if the package, a transitive dependency, its maintainer account, or the package registry distribution process were compromised.Attack Path
- An attacker compromises the npm package, a maintainer account, or a dependency resolved by
mcp-remote@latest. - The attacker publishes a malicious version that becomes the package's
latestrelease. - A user installs or launches the MCP server using the documented configuration.
npx -yretrieves the mutable latest release without an interactive confirmation step.- Package lifecycle logic or runtime code executes under the invoking user's account.
- The malicious code can perform actions permitted to that account, including reading accessible local files, accessing environment variables, initiating network connections, or modifying user-writable data.
Impact Assessment
Successful exploit ...[truncated 418 chars]
- An attacker compromises the npm package, a maintainer account, or a dependency resolved by
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@x.y.z; do not use a version range or mutable distribution tag. - Manage the package through a committed package manifest and lockfile so that both direct and transitive dependency versions are reproducible.
- Verify downloaded package integrity using the package manager's integrity metadata or an independently maintained checksum.
- Review the pinned package, its lifecycle scripts, and its transitive dependencies before deployment.
- Avoid automatic confirmation with
npx -yfor first-time or security-sensitive execution. Prefer an explicit installation and approval workflow. - Run the MCP process with least privilege in an isolated environment, exposing only the files, environment variables, and network destinations required for the Jikan integration.
- Establish a controlled dependency-update process that includes security review and testing before changing the pinned version.
- Replace
