T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23-34
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumVulnerable Code
bash pip3 install openaiThe alternative virtual-environment instructions repeat the same unpinned installation:
bash python3 -m venv ~/.openclaw/skills/kimi-search/venv source ~/.openclaw/skills/kimi-search/venv/bin/activate pip install openaiTechnical Analysis
The documented installation process retrieves the latest available
openaipackage and its transitive dependencies without a version constraint, lockfile, or package-hash verification. Consequently, the code installed by users can change after this Skill has been reviewed.This does not establish that the current package is malicious. However, it creates a supply-chain exposure in which a compromised, malicious, or unexpectedly incompatible future package release could be installed automatically. Python packages may execute code during installation or when imported by
scripts/kimi-search.py.Attack Path
- An attacker compromises a future release of the named package or one of its transitive dependencies.
- A user follows the Skill documentation and runs
pip3 install openaiorpip install openai. - The package manager retrieves the affected release because no reviewed version or hash is required.
- Malicious package code executes during installation or when the script imports the package.
- The code operates with the privileges and environment access of the user running the installation or Skill.
Impact Assessment
Successful exploitation could allow arbitrary code execution with the installing user's privileges. Depending on that user's access, the payload could read environment variables such as
MOONSHOT_API_KEY, access user-readable files, alter the Python environment, or make network requests. The scope is limited by the privileges and sand ...[truncated 61 chars]- Remediation
View remediation
Remediation Suggestions
- Add a dependency manifest that pins the
openaipackage and all transitive dependencies to reviewed versions. - Generate and verify cryptographic hashes, such as by using
pip install --require-hashes -r requirements.txt. - Use a reproducible lockfile and review dependency changes before updating it.
- Install dependencies from the official package index over TLS and avoid untrusted additional indexes.
- Run the Skill in an isolated virtual environment under a least-privileged account.
- Add automated dependency vulnerability and integrity scanning to the release process.
- Add a dependency manifest that pins the
