T08 · Insecure Dependencies
- Location
SKILL.md:48- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 48-56
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
json { "mcpServers": { "pipeworx-artic": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/artic/mcp"] } } }Technical Analysis
The MCP configuration invokes
npxwith the automatic-confirmation option (-y) and the mutable dependency specifiermcp-remote@latest. When the MCP server starts, npm may download and execute whichever package release is associated with thelatestdistribution tag at that time.Because the effective package code can change after this Skill has been reviewed, the local configuration does not provide a reproducible or auditable dependency boundary. Compromise of the npm package, its publisher account, or its release process could cause subsequently launched installations to execute attacker-controlled package code.
No evidence establishes that the current package is malicious. The vulnerability is the unsafe use of a mutable, automatically executed dependency rather than a confirmed malicious payload.
Attack Path
- An attacker compromises the npm package, its publisher credentials, or the package release process.
- The attacker publishes a malicious package version and assigns it to the
latestdistribution tag. - A user enables or starts the documented MCP configuration.
npx -ydownloads the version currently referenced bymcp-remote@latestwithout requesting interactive confirmation.- npm executes the downloaded package under the account that launched the MCP client.
- The malicious package can access files, environment variables, credentials, and network resources available to that account.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user ...[truncated 494 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed package version, such asmcp-remote@x.y.z. - Manage the dependency through a committed lockfile and require integrity verification using the package manager's recorded cryptographic hash.
- Preinstall the reviewed dependency during a controlled build or deployment phase rather than downloading it automatically when the MCP server starts.
- Remove
-ywhere practical so unexpected installation or package-resolution changes require explicit approval. - Use a trusted internal npm registry or allowlist and monitor the package for ownership changes, unexpected releases, and security advisories.
- Run the MCP process in a restricted environment with minimal filesystem access, sanitized environment variables, limited network access, and no administrative privileges.
- Re-audit and deliberately update the pinned version instead of inheriting changes through a mutable distribution tag.
- Replace
