T08 · Insecure Dependencies
- Location
SKILL.md:151- Finding
Unpinned Third-Party Python Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:151-153,README.md:14-18, andpackage.json:39-43
Vulnerability Type: Unpinned supply-chain dependencies
Risk Level: MediumVulnerable Code
SKILL.md:151-153:bash pip3 install scikit-learn numpy pandasREADME.md:14-18:bash pip3 install scikit-learn numpy pandaspackage.json:39-43:json "pip": [ "scikit-learn", "numpy", "pandas" ]Technical Analysis
The project instructs users and package tooling to install three third-party Python packages without exact version constraints, integrity hashes, or a lock file. Dependency resolution therefore selects package versions available from the configured Python package index at installation time rather than a reproducible set of previously reviewed artifacts.
Python package installation may execute package build-system or installation code with the privileges of the user running
pip. If a selected dependency release, transitive dependency, package-index account, distribution artifact, or configured package mirror is compromised, the effective installation behavior can change after this project has been audited.The reviewed project does not reference an untrusted package index or an apparent typosquatted package. The risk arises from unrestricted and non-reproducible dependency resolution rather than evidence that the currently named packages are malicious.
Attack Path
- An attacker compromises a declared dependency, one of its transitive dependencies, its publishing account, or a package mirror used by the victim.
- The attacker publishes an affected distribution containing malicious build or installation behavior.
- A user follows the documented
pip3 install scikit-learn numpy pandascommand, or compatible Skill tooling processes the unpinnedpiprequirements. - The package resolver selects and downloads the attacker-controlled rele ...[truncated 727 chars]
- Remediation
View remediation
Remediation Suggestions
-
Create a reviewed requirements file that pins every direct and transitive dependency to an exact version.
-
Record cryptographic hashes for all accepted distributions and enforce them with:
bash python3 -m pip install --require-hashes -r requirements.txt -
Generate and maintain the lock file with a dependency-management tool such as
pip-tools, and review dependency changes before updating it. -
Prefer binary wheels from the official package index where appropriate, and explicitly configure trusted package indexes rather than inheriting uncontrolled mirror settings.
-
Run dependency installation in a dedicated virtual environment or restricted container without administrator privileges.
-
Add automated dependency vulnerability and provenance scanning to the release process.
-
Update
SKILL.md,README.md, andpackage.jsonso that all installation paths reference the same pinned and verified dependency set.
-
