T08 · Insecure Dependencies
- Location
SKILL.md:43- Finding
Unpinned npm Dependency Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 43-50
Vulnerability Type: Unpinned third-party runtime dependency
Risk Level: HighVulnerable Code:
json { "mcpServers": { "pipeworx-dogceo": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/dogceo/mcp"] } } }Technical Analysis
The MCP configuration invokes
npxwith both-yand the mutable package specifiermcp-remote@latest. This causes npm to download and execute whichever package release is currently identified by thelatestdistribution tag without interactive confirmation.The effective code executed by this configuration can therefore change after the Skill has been reviewed. The configuration does not pin an audited version, verify a package integrity hash, or provide a lockfile. If the npm package, maintainer account, publication process, or dependency chain is compromised, malicious code can execute during MCP server startup.
Attack Path
- An attacker compromises the
mcp-remotepackage, a transitive dependency, or an authorized publisher account. - The attacker publishes a malicious release and assigns it the npm
latesttag. - A user or Agent starts the configured MCP server.
npx -ydownloads the malicious release without requesting confirmation.- npm executes the package locally as the user running the Agent.
- The malicious package can access resources available to that operating-system account.
Impact Assessment
Successful exploitation provides arbitrary code execution with the privileges of the user running the MCP configuration. Depending on the host environment, the malicious dependency could read accessible files and environment variables, steal credentials, alter project data, invoke network services, or install user-level persistence. The configuration does not itself elevate privileges, so access remains bound ...[truncated 52 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, audited package version. - Remove
-yso unexpected installation or package-resolution changes require explicit approval. - Install dependencies through a committed lockfile and use reproducible installation commands such as
npm ci. - Verify package provenance and integrity through registry signatures, integrity hashes, or an approved internal package mirror.
- Review the selected package and its transitive dependencies before deployment.
- Run the MCP process in a restricted environment with minimal filesystem access, sanitized environment variables, and constrained network permissions.
- Establish an explicit dependency-update process that includes review and security testing before changing the pinned version.
- Replace
