T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned npm Dependency Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23–24
Vulnerability Type: Unpinned executable dependency
Risk Level: HighVulnerable Code
json "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/numbersapi/mcp"]Technical Analysis
The configuration invokes
npxwith the mutable dependency referencemcp-remote@latest. The-yoption automatically approves installation, so the package selected by the npm registry is downloaded and executed without interactive confirmation.Because the
latesttag can be changed after this Skill has been reviewed, the code executed at runtime is not necessarily the code that existed during the audit. No exact version, lockfile, or package integrity hash constrains the downloaded artifact. This creates a supply-chain risk if a future release is malicious or if the package maintainer account, package, or registry delivery process is compromised.Attack Path
- An attacker compromises the npm package, its maintainer account, or the relevant package-distribution process.
- The attacker publishes a malicious release and assigns it to the mutable
latesttag. - A user starts the configured MCP server.
- The configuration runs
npx -y mcp-remote@latest. npxautomatically downloads and executes the attacker-controlled package without requesting confirmation.- The malicious package runs locally under the account and environment used to start the Agent.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the Agent user. Depending on that account's permissions and environment, malicious package code could access readable local files, environment variables, Agent-accessible credentials, and network resources; alter user-owned files; or launch additional processes.
The finding does not establish that the current
mcp-remotepackage is malicious. The risk arises because the documented config ...[truncated 118 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version, such asmcp-remote@<audited-version>. - Manage the dependency in a project manifest and lockfile rather than resolving it dynamically on every startup.
- Verify the package artifact using npm lockfile integrity metadata or an independently validated cryptographic checksum.
- Remove automatic approval through
-ywhere operationally feasible so unexpected installation behavior is visible to the user. - Review dependency updates before changing the pinned version, including package ownership, release provenance, dependency changes, and published artifact contents.
- Run the MCP client with least privilege in an isolated environment with restricted filesystem, credential, and network access.
- Replace
