T08 · Insecure Dependencies
- Location
SKILL.md:96- Finding
Unpinned Third-Party Package Installation Guidance
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 96–119
Vulnerability Type: Insecure third-party dependency installation
Risk Level: MediumVulnerable Code
bash # Core backtesting frameworks pip install backtrader pip install backtesting pip install vectorbt # Machine learning and AI quantitative tools pip install pybroker pip install qlib # Data acquisition pip install akshare pip install tushare pip install yfinance # Cryptocurrency tools pip install hummingbot pip install freqtrade pip install ccxt # Portfolio optimization pip install riskfolio-libThe comments above are translated from the source; the package-installation commands are reproduced verbatim.
Technical Analysis
The Skill's declared function is to catalog quantitative-finance resources, but its quick-install section recommends installing 13 third-party Python distributions without:
- Exact version constraints;
- Cryptographic hashes;
- A reviewed lockfile;
- An isolated virtual environment;
- Explicit package-index selection;
- Verification that each package name belongs to the referenced project.
Running these commands causes
pipto resolve mutable releases from the user's configured package index. Package installation may execute attacker-controlled build or installation logic. A compromised maintainer account, malicious release, dependency-confusion condition, or incorrectly associated package name could therefore result in arbitrary code execution.The local files do not establish that every package name—particularly
qlib—is the official distribution associated with its adjacent listed project. This does not prove that any listed package is malicious, but it makes unconditional installation unsafe without independent verification.These installations also exceed the minimum privileges necessary for a resource-list Skill. Merely presenting repository links requires neither dependency installation nor execution of third-party package code.
...[truncated 1478 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the bulk-install section because dependency installation is not required for the Skill's resource-catalog function.
- If installation guidance is retained, clearly mark every command as optional and direct users to each project's reviewed official installation documentation.
- Verify that every Python distribution name is owned or endorsed by the corresponding upstream project.
- Pin reviewed versions using exact constraints such as
package==x.y.z. - Use a lockfile containing hashes for all direct and transitive dependencies, and install with hash verification where practical.
- Require installation in a dedicated, non-privileged virtual environment or disposable container.
- Do not recommend
sudo pip, administrator execution, or installation into the system Python environment. - Specify a trusted package index and warn users that custom or inherited index configuration can introduce dependency-confusion risk.
- Review package provenance, release signatures, maintainers, build configuration, and transitive dependencies before updating pinned versions.
