T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 27
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumVulnerable Code
bash pip install ollama-herdTechnical Analysis
The setup instructions install
ollama-herdfrom the default Python Package Index without specifying a reviewed version or verifying an integrity hash. Consequently, the command resolves whichever release the package index currently considers appropriate.Python package installation may execute package-controlled build or installation logic. A compromised publisher account, malicious future release, or package-index compromise could therefore turn this documented setup step into a code-execution vector. The audit did not find evidence that the package is currently malicious; the finding concerns the absence of dependency pinning and integrity verification.
Attack Path
- An attacker compromises the package publisher account, distribution channel, or a future package release.
- The attacker publishes a malicious version under the expected
ollama-herdpackage name. - A user follows the Skill's setup instructions and runs
pip install ollama-herd. pipretrieves the attacker-controlled release because no version or hash is constrained.- Malicious installation or runtime logic executes with the privileges of the user running the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the invoking user's account. This may expose files, environment variables, credentials, model inputs, and network resources accessible to that account. The impact could be greater if the installation command is run from a privileged account or environment.
No evidence was found in the audited Skill itself of instruction hijacking, persistence, credential theft, destructive behavior, obfuscated payloads, or embedded malicious scripts.
- Remediation
View remediation
Remediation Suggestions
-
Pin the package to a specifically reviewed version, for example:
bash python3 -m pip install "ollama-herd==REVIEWED_VERSION" -
Publish a lock file or requirements file containing cryptographic hashes, and install with hash enforcement:
bash python3 -m pip install --require-hashes -r requirements.txt -
Prefer an isolated virtual environment rather than installing into a system or privileged Python environment.
-
Document the expected package publisher, repository, version, and artifact hashes so users can verify provenance.
-
Establish a controlled update process in which new releases are reviewed and tested before the pinned version and hashes are changed.
-
Explicitly warn users not to run the installation command with elevated privileges.
-
