T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14-16
Vulnerability Type: Unpinned runtime dependency and insufficient supply-chain integrity controls
Risk Level: MediumVulnerable Code
markdown ## Requirements - Python 3.10+ - `google-generativeai` package (`pip install google-generativeai`) - `GEMINI_API_KEY` in `/Users/edwin/.openclaw/workspace/dreams-arts/.env`Technical Analysis
The documented installation command retrieves the latest available version of
google-generativeaiand its transitive dependencies without pinning versions or verifying package hashes. Consequently, installation is not reproducible, and the code ultimately installed can change after the skill has been audited.The package name does not appear to be an evident typosquat, and the audit found no proof that the current package is malicious. The risk arises from trusting mutable upstream packages without version or integrity constraints. A future compromised release, compromised transitive dependency, or incompatible update could execute code during installation or when
autopilot.pyimports the package.Attack Path
- An attacker compromises an upstream package release, its publishing credentials, or one of its unpinned transitive dependencies.
- A user follows the documented
pip install google-generativeaiinstruction. - Package resolution selects the attacker-controlled or compromised version because no audited version is pinned.
- Malicious code executes during package installation or when
google.generativeaiis imported. - That code runs with the operating-system permissions of the user running the installation or skill.
Impact Assessment
A compromised dependency could obtain the same privileges as the invoking user. Depending on that user's permissions, this could allow access to local files, environment variables, API credentials, network resources, and generated content. It c ...[truncated 254 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
google-generativeaito a specifically reviewed version rather than installing the latest release. - Lock every transitive dependency through a generated lock file or fully pinned requirements file.
- Record and verify package hashes, such as with
pip install --require-hashes -r requirements.txt. - Review dependency updates before changing the lock file, and use automated vulnerability and provenance checks.
- Install dependencies in a dedicated virtual environment with only the permissions required by this skill.
- Update
SKILL.mdso its installation instructions reference the audited, hash-verified dependency file.
- Pin
