T08 · Insecure Dependencies
- Location
SKILL.md:332- Finding
Unpinned Third-Party Python Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 332–333
Vulnerability Type: Supply-chain risk from unpinned dependencies
Risk Level: MediumVulnerable Code
markdown | jieba | 中文分词 | 推荐 | pip install jieba | | networkx | 关系图谱 | 推荐 | pip install networkx |Technical Analysis
The installation instructions direct users or agents to install
jiebaandnetworkxwithout fixed versions, package hashes, a lockfile, or an explicitly trusted package index. As a result,pipresolves mutable package releases at installation time rather than installing artifacts that were reviewed as part of this Skill.Python package installation can execute dependency-controlled build or installation logic. If an upstream release or package-distribution account is compromised, or package resolution is redirected to an unsafe index, following these instructions could install and execute code that was not present during the audit.
No malicious package or active compromise was identified. This finding concerns unsafe dependency-resolution practices and the resulting exposure to future supply-chain compromise.
Attack Path
- A user or agent follows the dependency instructions in
SKILL.md. - It runs
pip install jiebaorpip install networkx. pipresolves the current package release and transitive dependencies from its configured index.- An attacker who has compromised an upstream release, distribution account, dependency, or configured package index supplies a malicious artifact.
- Package-controlled build or installation logic executes with the privileges of the user running
pip. - The installed package can execute again when imported or otherwise used during novel analysis.
Impact Assessment
Exploitation would execute code with the privileges of the account running the installation or analysis process. Depending on that account's access, an attacker could read or modify proje ...[truncated 371 chars]
- A user or agent follows the dependency instructions in
- Remediation
View remediation
Remediation Suggestions
- Pin every direct dependency to a reviewed, exact version, for example through a version-controlled requirements file.
- Pin transitive dependencies with a generated lockfile rather than relying only on top-level version constraints.
- Require verified artifact hashes, such as with
pip install --require-hashes -r requirements.txt. - Explicitly use a trusted package index and avoid unreviewed extra indexes or mirrors.
- Install dependencies in a dedicated virtual environment under a non-privileged account.
- Add automated dependency vulnerability and integrity scanning to the release process.
- Review dependency updates before regenerating version pins and hashes.