T08 · Insecure Dependencies
- Location
SKILL.md:266- Finding
Unverified and Unpinned Executable Python Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 266-269
Vulnerability Type: Insecure third-party dependency installation
Risk Level: MediumComplete Code Snippet:
markdown - **Dependency installation command**: `pip install futures-quant pandas numpy` ### Five-step operation guide 1. **Install dependencies**: Run `pip install futures-quant pandas numpy`Technical Analysis
The skill directs users or an agent with execution capability to install
futures-quant,pandas, andnumpyfrom the default Python package index without exact version pins, integrity hashes, a lockfile, verified publisher information, or a source repository suitable for code review.The repository itself contains only
SKILL.md, so the executable contents and provenance of the package namedfutures-quantcannot be verified from the audited artifact. Because package installation and subsequent import can execute package-controlled code, resolving a mutable or compromised distribution creates a supply-chain execution boundary. The risk is especially relevant because the skill declares theexectool and describes workflows involving financial data, trading systems, and environment-based API credentials.This finding does not establish that the referenced package is malicious. It establishes that the documented installation process lacks controls needed to ensure that the installed artifact is the intended, reviewed version.
Attack Path
- A user or agent loads the skill and follows its dependency-installation guidance.
- The command invokes
pipagainst its configured package index and resolves packages without fixed versions or required hashes. - An attacker compromises the referenced distribution, its publisher account, the configured package index, or a future mutable release.
pipdownloads and installs the attacker-controlled package artifact.- Package build or installation behavior, or t ...[truncated 1035 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the installation command until the identity and provenance of
futures-quantcan be independently verified. - Pin every dependency to a reviewed exact version rather than allowing mutable resolution.
- Generate and enforce cryptographic hashes, such as with a hash-locked requirements file and
pip install --require-hashes. - Publish the authoritative source repository, package publisher identity, release-signing information, and reproducible build process.
- Use a dependency lockfile and automated software-composition analysis to monitor vulnerabilities and unexpected ownership or release changes.
- Install dependencies in an isolated virtual environment or container under a dedicated, least-privilege account.
- Prevent the installation environment from accessing production trading credentials and live trading interfaces.
- Separate dependency installation from strategy execution, require explicit user approval, and review package contents before import.
- Restrict package installation to an approved internal index or allowlist after artifact verification.
- Remove the installation command until the identity and provenance of
