T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned Third-Party SDK Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 35-40
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumComplete Code Snippet:
bash python3 -m venv .venv . .venv/bin/activate python -m pip install dashscopeTechnical Analysis
The installation command retrieves the latest available
dashscopepackage and its transitive dependencies without an exact version constraint, lock file, or integrity hashes. Consequently, the code installed when users follow these instructions can change after this Skill has been reviewed.This creates a supply-chain exposure: a compromised future package release or transitive dependency could introduce malicious code. Python package installation may execute build-related code, and installed package code would execute when imported or invoked later. The use of a virtual environment limits package placement but does not sandbox package behavior from the installing user's files, environment variables, or network access.
Attack Path
- An attacker compromises the
dashscopepackage or one of its resolved dependencies and publishes a malicious release. - A user or agent follows the instructions in
SKILL.md. pipresolves and downloads the mutable malicious release because no audited version or hash is specified.- Malicious code executes during package installation, build processing, or subsequent SDK use.
- The code operates with the privileges of the user running the command and may access files, environment variables, and credentials available to that process.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. The affected scope may include the project workspace, user-accessible files, outbound network access, and environment credentials such as
DASHSCOPE_API_KEYif present during installation or execution.No evidence indicates that the curren ...[truncated 100 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
dashscopeto an exact version that has been reviewed and tested. - Record all transitive dependencies in a lock file.
- Require cryptographic hashes during installation, for example:
bash python -m pip install --require-hashes -r requirements.txt - Obtain packages only from the expected official package index or an organization-controlled mirror.
- Review and deliberately update the lock file rather than automatically consuming new releases.
- Run installation with minimal user privileges and avoid exposing cloud credentials to the installation process.
- Pin
