T08 · Insecure Dependencies
- Location
SKILL.md:97- Finding
Unpinned Third-Party VCS Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 97
Vulnerability Type: Unpinned dependency installed from a mutable remote Git repository
Risk Level: MediumVulnerable Code
markdown - Install: `pip install git+https://github.com/akdira/okf-toolkit.git`Technical Analysis
The documented command instructs users or agents to install Python code directly from the default branch of a third-party GitHub repository. It specifies neither a reviewed release version nor an immutable commit hash. Consequently, the code retrieved by the same command can change after the skill has been audited.
Python package installation can execute dependency-controlled build or installation logic. Trusting a mutable remote branch therefore creates a supply-chain risk: compromise of the repository, its maintainer account, or its ownership could turn this instruction into an arbitrary-code-execution vector.
The referenced repository is also hosted under an individual account rather than the Google Cloud organization associated with the specification mentioned elsewhere in the document. This does not establish maliciousness, but it increases the importance of immutable version pinning and independent provenance verification.
Attack Path
- An attacker compromises the repository, its maintainer account, or another mechanism capable of changing its default branch.
- The attacker adds malicious package build, installation, or runtime code.
- A user or agent follows the installation command in
SKILL.md. pipretrieves the repository’s current mutable revision rather than the revision originally reviewed.- Malicious package-controlled code executes during installation or subsequent CLI use.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the user running
pip. Depending on those privileges and the local environment, the malicious dependency could access user-readable files, cre ...[truncated 348 chars]- Remediation
View remediation
Remediation Suggestions
- Replace the mutable-branch installation command with an exact, reviewed release version from a trusted package registry where possible.
- If installation from Git is necessary, pin the URL to a full immutable commit hash, for example:
bash pip install "git+https://github.com/akdira/okf-toolkit.git@FULL_REVIEWED_COMMIT_HASH" - Record and verify the expected source revision and package provenance before installation.
- Use a lock file or requirements file with cryptographic hashes where the distribution mechanism supports it, and enforce installation with
pip --require-hashes. - Review the dependency’s package metadata, build configuration, transitive dependencies, and relevant source code before approving a pinned revision.
- Install the tool in an isolated virtual environment or container under a non-privileged account.
- Avoid administrator or root installation and restrict access to credentials, sensitive files, and unnecessary network resources during installation and execution.
