T08 · Insecure Dependencies
- Location
SKILL.md:32- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:32
Vulnerability Type: Unpinned package installation from a mutable package index
Risk Level: Mediumbash pip install dashscopeTechnical Analysis
The installation instructions retrieve
dashscopewithout a version constraint, lockfile, package hash, or explicit trusted repository. Consequently, the package resolved during installation can change after the skill has been reviewed.This creates supply-chain exposure if a future package release, package-publishing account, configured Python package index, or upstream distribution channel is compromised. Python packages can execute code during installation and whenever imported by
scripts/cli.py, so a malicious resolved package could run with the privileges of the user operating the skill.No evidence was found that the current
dashscopepackage is malicious. The vulnerability is the absence of controls that ensure users install the same reviewed dependency artifact.Attack Path
- An attacker compromises the package publisher, publishing credentials, upstream package index, or a package source configured in the victim's pip environment.
- The attacker makes a malicious
dashscoperelease or replacement artifact available for resolution. - A user follows the documented
pip install dashscopecommand. - Because no version or hash is enforced, pip resolves and installs the attacker-controlled artifact.
- Malicious code executes during installation or when
scripts/cli.pyimportsdashscope. - The code operates with the invoking user's permissions and may access the
DASHSCOPE_API_KEY, local audio files, and other data available to that account.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the account performing installation or transcription. The reachable scope includes environment variables, submitted audio files, files readable by t ...[truncated 219 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
dashscopeto a reviewed, exact version rather than resolving the latest available release. - Maintain dependencies in a lockfile or requirements file containing cryptographic hashes.
- Install with hash verification, for example through
pip install --require-hashes -r requirements.txt. - Document and enforce the official trusted package index instead of inheriting arbitrary pip index configuration.
- Review dependency updates before changing the pinned version and use automated vulnerability and provenance checks.
- Run installation and transcription as an unprivileged user in an isolated environment with access limited to the required audio file and API credential.
- Pin
