T08 · Insecure Dependencies
- Location
SKILL.md:67- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
=0.3.0`, that open-ended constraint does not guarantee that the installed package is the release that was reviewed. Python packages can execute package build logic during installation and application code when imported. Consequently, a compromised upstream release, malicious transitive dependency, or unexpected future release could introduce code that is absent from this audited project. ### Attack Path 1. An attacker compromises the `histrategy-sdk` distribution account or one of its transitive dependencies. 2. The attacker publishes a malicious release that satisfies the unrestricted installation command. 3. A user follows the documented `pip install histrategy-sdk` instruction. 4. Pip retrieves the malicious release or dependency. 5. Attacker-controlled code executes during package installation or when the installed package is imported by the application. ### Impact Assessment The malicious package would execute with the privileges of the user running pip or the game. Depending on those privileges, it could access application data, game state, environment variables containing LLM API keys, and other files available to that account. If installation is performed with elevated privileges, the impact could extend to system-wide code execution and modification. ]]>- Remediation
View remediation
=0.3.0` metadata requirement with an exact reviewed version or a tightly controlled compatible range. - Generate dependencies from a trusted build process and scan each resolved package for known vulnerabilities. - Install dependencies in an isolated virtual environment under a nonprivileged account. - Configure pip to use an explicitly trusted package index and monitor package ownership and release changes. ]]>
