T08 · Insecure Dependencies
- Location
SKILL.md:77- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:77
Vulnerability Type: Unpinned dependency and non-reproducible installation
Risk Level: MediumVulnerable Code
text 3. Install dependency: `pip install requests`Technical Analysis
The documented installation command retrieves the latest version of
requestsand its transitive dependencies available at installation time. It provides no version constraints, lock file, or package integrity hashes.Although
requestsis a legitimate package from the expected public registry, this installation process is not reproducible. A future compromised release, compromised transitive dependency, or unexpected dependency-resolution change would be installed automatically. Package installation may execute build or installation logic with the privileges of the user runningpip.No evidence was found that the project intentionally references a typosquatted package, an untrusted package index, or a currently malicious release. The risk arises from inadequate supply-chain controls.
Attack Path
- An attacker compromises a future release of
requestsor one of its resolved transitive dependencies. - A user follows the documented
pip install requestsinstruction after the compromised version becomes available. pipresolves and downloads the compromised package because no trusted version or hash is specified.- Malicious installation or runtime code executes in the user's Python environment.
- The malicious package gains access to data and permissions available to that user, potentially including
NVIDIA_API_KEYwhen the Skill runs.
Impact Assessment
Successful exploitation could execute arbitrary Python code with the installing or runtime user's privileges. Depending on the environment, this may expose local files, environment variables, NVIDIA API credentials, network access, and data processed by the Skill. The code does not request ...[truncated 123 chars]
- An attacker compromises a future release of
- Remediation
View remediation
Remediation Suggestions
- Add a dependency manifest with an explicitly audited
requestsversion. - Generate and commit a lock file that fixes all transitive dependency versions.
- Require package hashes for integrity verification, for example:
bash python -m pip install --require-hashes -r requirements.txt - Install dependencies from the official package index over HTTPS and avoid untrusted extra indexes.
- Use an isolated virtual environment with only the permissions required by the Skill.
- Add automated dependency vulnerability and update monitoring so pinned packages can be upgraded deliberately after review.
- Add a dependency manifest with an explicitly audited
