T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13–18 and 37
Vulnerability Type: Unpinned third-party dependencies and mutable package execution
Risk Level: MediumVulnerable Code
bash # If npm/npx is unavailable npm install -g mcporterbash npx mcporter --helpbash mcporter mcp add minimax-mcpTechnical Analysis
The Skill directs users to install or execute
mcporterby package name without specifying an exact version, integrity hash, verified publisher, or trusted registry. Thenpxcommand may retrieve and immediately execute the package version currently served by the configured npm registry.The Skill also adds
minimax-mcpwithout identifying an exact reviewed version or immutable source. Consequently, the components executed during future installations may differ from those present when the Skill was audited. This creates a supply-chain trust boundary in which a compromised publisher account, malicious package update, dependency confusion condition, registry compromise, or package substitution could introduce arbitrary executable code.The global installation form increases exposure because package installation scripts and runtime code execute with the invoking user's permissions and place software in a shared environment. The configured MiniMax credential may also be available to subsequently executed MCP components.
Attack Path
- An attacker compromises a referenced package, its publisher account, one of its transitive dependencies, or the package-distribution channel.
- The attacker publishes a malicious release under the mutable package name.
- A user follows the Skill instructions and runs
npm install -g mcporter,npx mcporter --help, or adds the unpinnedminimax-mcpserver. - The package manager retrieves the malicious current release because no reviewed version or integrity value is enforced.
- Installation hooks or package ...[truncated 917 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
mcporterand the MiniMax MCP server to exact versions that have been reviewed. - Document the official package registry, canonical package names, expected publishers, and immutable source repositories.
- Use lockfiles and package integrity hashes where supported, and verify downloaded artifacts before execution.
- Prefer a project-local installation over
npm install -gto reduce shared-environment exposure and improve reproducibility. - Avoid implicit
npxdownloads. Usenpx --no-installwith a previously verified local dependency or invoke the pinned local binary directly. - Disable or strictly control package installation scripts where feasible.
- Run MCP components under a dedicated, least-privileged account or sandbox with restricted filesystem and network access.
- Expose
MINIMAX_API_KEYonly to the process that requires it, rotate it periodically, and ensure it is not written to logs. - Establish a dependency-update review process that checks provenance, signatures, integrity values, release changes, and transitive dependencies before changing pinned versions.
- Pin
