T08 · Insecure Dependencies
- Location
SKILL.md:330- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 330-330 and 470-470
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumVulnerable Code
bash pip install requestsThe dependency table repeats the same installation instruction:
text requests | Python library | Required | pip install requestsTechnical Analysis
The Skill directs the Agent to install
requestswithout specifying an audited version, verifying a package hash, or using a locked dependency manifest. Consequently, the installed code depends on whichever release and package index resolution are current when the command runs.Although
requestsis a legitimate package and no malicious package is explicitly named, this installation pattern provides weaker supply-chain integrity than necessary. A compromised upstream release, compromised package index, or manipulated package-index configuration could cause unreviewed code to enter the execution environment.Package installation may execute package build or installation logic under the privileges of the user running the Agent. The risk is therefore not limited to the later behavior of the imported library.
Attack Path
- An attacker compromises an upstream dependency release or influences the Python package index used by the environment.
- The Agent follows the Skill instructions and runs
pip install requests. pipresolves and downloads an unpinned package release without hash verification.- Package installation or build logic executes with the Agent user's privileges.
- The compromised package can access files, environment variables, network resources, and other assets available to that user.
This attack path requires compromise or manipulation of the dependency supply chain; the audited Skill does not itself provide such a malicious package.
Impact Assessment
Successful exploitation could permit arbitrary code exec ...[truncated 360 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the unversioned installation command with a dependency lock file containing an audited version.
- Require hashes using a command such as
pip install --require-hashes -r requirements.txt. - Configure installation to use the official trusted package index explicitly.
- Install dependencies in an isolated virtual environment with minimal filesystem and network permissions.
- Use automated dependency scanning and a controlled update process rather than resolving the newest release during every run.
- Avoid automatically executing installation commands without explicit user approval.
