T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Unpinned Third-Party MCP Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47–52
Vulnerability Type: Supply-chain risk caused by unpinned remote package execution
Risk Level: MediumVulnerable Code
json { "conviction": { "command": "npx", "args": ["-y", "conviction-mcp"] } }Technical Analysis
The MCP configuration invokes
npx -y conviction-mcpwithout pinning the package to an exact, reviewed version or verifying its integrity. If the package is not already available locally,npxcan retrieve it from the configured npm registry and execute its package-defined code. The-yoption suppresses the installation confirmation.Consequently, the code that runs can change after this Skill has been reviewed. Security depends on the continuing integrity of the npm account, package releases, package dependencies, registry resolution, and the user's npm configuration. The repository contains no lockfile, integrity hash, provenance requirement, or sandbox policy that constrains this execution.
This finding identifies an unsafe dependency-execution pattern; the audited file does not establish that the current
conviction-mcppackage is malicious.Attack Path
- An attacker compromises the
conviction-mcppublishing account, one of its transitive dependencies, or the registry/package-resolution path. - The attacker publishes or causes resolution to a malicious package version.
- A user applies the documented MCP configuration.
npx -y conviction-mcpretrieves the currently resolved package without requesting confirmation.- The package's executable code runs under the operating-system account and environment of the Agent process.
- Malicious code can attempt to access resources available to that account and process, including readable files, environment variables, network services, and MCP-related data.
Impact Assessment
Successful exploitation could provide arbitrary code ...[truncated 536 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
conviction-mcpto an exact, reviewed version rather than relying on the latest registry resolution. - Verify package ownership, source repository, release provenance, and npm registry metadata before use.
- Use lockfile and integrity verification where supported, and review both direct and transitive dependencies.
- Remove
-yso installation or retrieval requires explicit operator confirmation. - Prefer a locally installed, audited artifact or a package obtained through a controlled internal registry.
- Run the MCP server in a sandbox or container with a read-only filesystem where practical, restricted environment variables, minimal network access, and no unnecessary host credentials.
- Ensure wallet and Agent permissions follow least privilege, even if the documented currency is limited to Solana devnet test assets.
- Establish a controlled update process requiring security review before changing the pinned package version.
- Pin
