T08 · Insecure Dependencies
- Location
SKILL.md:154- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 154–156 and line 247
Vulnerability Type: Supply-chain risk from unpinned dependencies
Risk Level: MediumVulnerable Code
Lines 154–156:
bash pip3 install matplotlib pip3 install numpy pip3 install pandasLine 247:
bash pip3 install matplotlib numpy pandasTechnical Analysis
The Skill directs users or execution-capable agents to install third-party Python packages without version constraints, cryptographic hashes, a lockfile, or an isolated environment. Package installation can execute package build and installation logic with the privileges of the invoking process.
Although the named packages are established projects and the audited file does not specify a malicious package or custom package index, resolving mutable package names at installation time creates a supply-chain exposure. A compromised release, compromised package registry, malicious index configuration, or unexpected future version could introduce unwanted code after the Skill has already been reviewed.
The document also claims that the tool operates entirely without network access, but these installation commands normally contact a package registry unless dependencies are already cached. This inconsistency may prevent users from recognizing that external artifacts are being retrieved.
Attack Path
- A user or agent follows the dependency-installation instructions.
pip3resolves the unpinned package names using the active Python package-index configuration.- Package distributions and any required transitive dependencies are retrieved from mutable external sources or local mirrors.
- Installation or build hooks execute under the invoking account.
- If a resolved artifact, dependency release, configured mirror, or package-index channel has been compromised, attacker-controlled code executes locally.
- The resulting package remains install ...[truncated 909 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every direct dependency to a reviewed version rather than installing unconstrained package names.
- Provide a lockfile that also fixes transitive dependency versions.
- Require cryptographic hashes, such as through a hash-locked requirements file and
pip install --require-hashes. - Install dependencies in a dedicated virtual environment instead of the global or system Python environment.
- Explicitly prohibit administrator or root installation and document a least-privilege setup procedure.
- Separate dependency provisioning from routine Skill execution so an agent cannot silently install packages during normal chart generation.
- Use a trusted, controlled package index or an internally reviewed artifact repository.
- Add dependency vulnerability and integrity scanning to the release process.
- Correct the documentation to disclose that initial dependency retrieval may require network access.
- Supply the referenced implementation scripts and a reproducible dependency manifest so reviewers can audit the actual runtime behavior.
Example hardened installation workflow:
bash python3 -m venv .venv .venv/bin/python -m pip install --require-hashes -r requirements.lock
