T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party Dependencies Create Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:4,SKILL.md:119,README.md:30-32
Vulnerability Type: Unpinned dependency installation
Risk Level: MediumVulnerable Code
json metadata: {"clawdbot":{"emoji":"📊","requires":{"bins":["python3"],"env":["QVERIS_API_KEY"]},"install":[{"id":"python-deps","kind":"pip","package":"efinance akshare pandas numpy","label":"Install Python dependencies"}]}}bash pip install efinance akshare pandas numpyTechnical Analysis
The Skill installs
efinance,akshare,pandas, andnumpywithout exact version constraints, package hashes, a lock file, or an explicitly trusted package index. Consequently, installation resolves whatever versions are current on the configured Python package index at installation time.Python package installation can execute package-controlled build logic. The effective installation payload may therefore change after this Skill has been reviewed. Although the package names do not appear to be misspelled and no dependency is confirmed as malicious, the current configuration does not provide reproducible or integrity-verified dependency resolution.
This exposes users to compromised future releases, compromised publisher accounts, dependency confusion through an untrusted package index, and malicious transitive dependencies.
Attack Path
- An attacker compromises a declared package, one of its transitive dependencies, or the package index used by the victim.
- The attacker publishes a malicious release that still satisfies the unconstrained package name.
- A user installs the Skill dependencies using the documented command or automatic Skill installer.
- Pip resolves and downloads the malicious release.
- Package-controlled build or installation code executes with the privileges of the user running pip.
- Malicious code may also execute later when the application imports the affected package.
Impact Assessment
Successful exploitation could ...[truncated 623 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every direct dependency to a reviewed exact version.
- Generate and commit a lock file that includes all transitive dependencies.
- Record cryptographic hashes and install with
pip install --require-hashes. - Configure an explicitly trusted package index instead of inheriting an arbitrary environment configuration.
- Scan dependencies for known vulnerabilities during development and release.
- Review dependency updates before changing locked versions.
- Prefer installation in an isolated, unprivileged virtual environment.
- Document the exact supported Python and dependency versions.
