T08 · Insecure Dependencies
- Location
SKILL.md:140- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 140
Vulnerability Type: Unpinned and unverified third-party dependency installation
Risk Level: MediumVulnerable Code Snippet:
markdown ## What You Need - Python 3.10+ - `pip install tokensave` - Analyze mode: nothing else — no API keys, no network, no config - Pipeline mode (separate): requires `OPENAI_API_KEY` and makes API callsTechnical Analysis
The installation instruction uses
pip install tokensavewithout specifying an audited version, cryptographic hash, trusted package index, or verifiable source revision. Consequently, the installed artifact is determined by the state of the configured Python package index at installation time.This creates a supply-chain risk because a compromised package release, compromised package repository, dependency-confusion condition, or malicious index configuration could cause attacker-controlled content to be installed. Python package installation may execute package-controlled build or installation logic, and the installed CLI subsequently runs with the invoking user's privileges.
The project contains only
SKILL.md; no implementation or dependency lock data is included. Therefore, the document's claims that analysis is local and does not make network calls cannot be independently verified against the installed package from the audited artifact alone. This audit does not establish that the currenttokensavepackage is malicious; the issue is the unsafe, mutable installation mechanism.Attack Path
- An attacker compromises the package, one of its transitive dependencies, the configured package index, or package-resolution infrastructure.
- The attacker publishes a malicious release that resolves under the unpinned
tokensaverequirement. - A user follows the documented
pip install tokensaveinstruction. pipretrieves the attacker-controlled package or dependency because ...[truncated 861 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specifically reviewed version, such as
tokensave==<audited-version>. - Distribute a requirements or lock file containing cryptographic hashes and install with
pip install --require-hashes -r requirements.txt. - Explicitly specify the trusted package index or verified source repository rather than relying on ambient pip configuration.
- Verify package provenance through signed releases, repository tags, and reproducible build artifacts where available.
- Pin and hash all transitive dependencies, not only the top-level package.
- Recommend installation in an isolated virtual environment under a non-privileged account.
- Include the audited implementation or a verifiable source revision in the skill package so claims concerning local processing and network behavior can be reviewed.
- Perform automated dependency and provenance checks before updating the documented version.
- Pin the dependency to a specifically reviewed version, such as