T08 · Insecure Dependencies
- Location
SKILL.md:73- Finding
Unpinned Third-Party Packages Are Installed and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:73-84;README.md:64-75
Vulnerability Type: Supply-chain exposure through unpinned dependencies
Risk Level: HighVulnerable Code
SKILL.md:73-84:bash npm install -g mcporterbash mcporter config add MiniMax \ --command uvx \ --args "minimax-coding-plan-mcp -y" \ --env MINIMAX_API_KEY=$MINIMAX_API_KEY \ --env MINIMAX_API_HOST=https://api.minimaxi.com \ --scope homeThe same unpinned installation and configuration instructions appear in
README.md:64-75.Technical Analysis
The installation instructions globally install the latest available
mcporternpm package without a pinned version or integrity verification. The MCP configuration then usesuvxto retrieve and runminimax-coding-plan-mcpwithout a pinned version or package hash. The-yargument further indicates unattended execution.Consequently, the code that executes is not fixed to the version reviewed in this audit. A compromised publisher account, malicious future release, dependency confusion event, or upstream package compromise could change the effective executable payload after the Skill has been reviewed.
Global npm installation also increases exposure because package installation scripts can execute with the installing user's privileges and affect commands available throughout that user's environment.
Attack Path
- An attacker compromises an upstream npm or Python package, its publisher account, or one of its transitive dependencies.
- The attacker publishes a malicious release under the package name used by the Skill.
- A user follows the documented unpinned installation instructions or invokes the
uvx-configured MCP service. - The package manager retrieves and executes the malicious release.
- The malicious package executes with the user's privileges and may access inherited environment variables, local files ...[truncated 555 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin exact versions of both
mcporterandminimax-coding-plan-mcp. - Verify package integrity using trusted lockfiles, hashes, signatures, or package-manager integrity metadata.
- Review and pin all transitive dependencies.
- Remove unattended execution flags where practical.
- Install dependencies in a dedicated, unprivileged virtual environment rather than globally.
- Use a controlled internal registry or verified package source for production deployments.
- Document the verified publisher, package version, checksum, and upgrade-review procedure.
- Re-audit dependency changes before updating pinned versions.
- Pin exact versions of both
