T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14-16
Vulnerability Type: Unpinned and unverified external dependency installation
Risk Level: MediumVulnerable Code:
bash pip install coolapk-mcpTechnical Analysis
The Skill instructs users to install
coolapk-mcpdirectly from the package index without specifying an exact version or verifying an integrity hash. The repository does not include the dependency's implementation, a lock file, checksums, a trusted package-index configuration, or another mechanism that binds installation to a reviewed artifact.Python package installation may execute package-controlled build or installation logic. Subsequent use of the installed
coolapkexecutable also runs code that is outside the audited project. Consequently, the effective behavior can change when a new package release is published, even if this Skill remains unchanged.README.mdalso states that the dependency is automatically installed through pip on first use, but the reviewed project contains no implementation showing how that installation is performed.Attack Path
- A user installs or loads the Skill and follows its prerequisite instructions.
- The user runs
pip install coolapk-mcp. - Pip resolves the package version available from the configured package index at that time.
- If the package account, package index, release pipeline, or resolved distribution has been compromised, pip downloads the attacker-controlled artifact.
- Package-controlled installation logic or the subsequently invoked CLI executes with the user's operating-system privileges.
- The malicious dependency could access files, environment variables, authentication material passed to the CLI, and network resources available to that user.
This path is conditional on compromise or malicious alteration of the external dependency. The audited files contain no evidence that the current package is mal ...[truncated 450 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact, reviewed version rather than installing the latest release.
- Publish a lock file containing cryptographic hashes and install with hash verification, such as
pip install --require-hashes. - Document the expected package index and prevent fallback to untrusted indexes.
- Reference the exact source revision corresponding to the pinned distribution.
- Review the package's source, build configuration, and transitive dependencies before approving upgrades.
- Prefer installation in an isolated virtual environment with minimal filesystem and network privileges.
- Do not perform automatic dependency installation without explicit user confirmation and a clear display of the exact version and source.
