T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Locations:
SKILL.md:27,README.md:8
Vulnerability Type: Supply-chain exposure through unpinned dependencies
Risk Level: MediumVulnerable Code Snippet:
SKILL.md:27bash pip install edge-ttsREADME.md:8bash pip install edge-ttsTechnical Analysis
The documented installation command installs the latest version of
edge-ttsand its transitive dependencies without a version constraint, lock file, or integrity hash. Consequently, the code installed by users can change after the Skill has been reviewed.Although no evidence establishes that the current package is malicious, this installation method creates supply-chain exposure. A compromised package release, compromised maintainer account, malicious transitive dependency, or unexpected incompatible release could introduce arbitrary code into the Skill's runtime environment.
Attack Path
- An attacker compromises the
edge-ttsdistribution channel, a maintainer account, or one of its unresolved transitive dependencies. - The attacker publishes a malicious version that still satisfies the unrestricted installation command.
- A user follows the project documentation and executes
pip install edge-tts. - Pip resolves and installs the attacker-controlled release.
- Malicious package code executes during installation or when
voice_sender.pyimports or invokes the dependency.
Impact Assessment
Successful exploitation could execute arbitrary Python code with the privileges of the user performing installation or running the Skill. This may permit access to user-readable files, OpenClaw configuration, environment variables, messaging credentials, and network resources available to that account. The issue does not independently provide root privileges unless installation or execution is performed with elevated privileges.
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
edge-ttsto a specifically reviewed version rather than resolving the latest release. - Maintain a lock file containing exact versions of all transitive dependencies.
- Require package hashes, for example through a hash-locked requirements file and
pip install --require-hashes. - Install packages only from an explicitly configured trusted index.
- Perform dependency vulnerability and provenance checks before updating the pinned version.
- Run the Skill in an isolated virtual environment under a non-privileged account.
- Update both
SKILL.mdandREADME.mdso users consistently follow the hardened installation procedure.
- Pin
