T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 16
Vulnerability Type: Unpinned dependency installation from a mutable package registry
Risk Level: MediumVulnerable Code:
bash pip install ollama-herd # install Ollama Herd from PyPI herd # start the Ollama router herd-node # start an Ollama node agent (run on each device)Technical Analysis
The installation instructions retrieve
ollama-herdfrom PyPI without specifying an audited version or verifying package integrity. Because the package reference is mutable, a future release or compromised registry account could introduce behavior that was not present when this Skill was reviewed.Python package installation can invoke package-controlled build backend logic. The instructions also immediately run the installed
herdandherd-nodeentry points. Consequently, malicious package code could execute with the privileges of the user performing the installation.The flagged pipelines at lines 34, 47, and 65 are not remote script execution. Commands such as:
bash curl -s http://localhost:11435/fleet/status | python3 -m json.toolpass a localhost HTTP response to Python's standard JSON formatter rather than to a shell. These read-only requests are consistent with the Skill's fleet-monitoring purpose and do not independently constitute remote payload retrieval and execution.
Attack Path
- An attacker compromises the PyPI publisher account, package release process, or another relevant supply-chain component.
- The attacker publishes a malicious version of
ollama-herdunder the existing package name. - A user follows the documented
pip install ollama-herdinstruction. - Pip retrieves the current attacker-controlled release because no version or cryptographic hash is required.
- Malicious code may execute during package build or installation, or when th ...[truncated 687 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specifically reviewed release, for example:
bash python3 -m pip install "ollama-herd==1.5.3" - Publish a lock file containing cryptographic hashes and install with hash enforcement:
bash python3 -m pip install --require-hashes -r requirements.lock - Verify that the pinned PyPI artifact corresponds to the reviewed source revision and document the expected artifact hashes.
- Prefer installation inside an isolated virtual environment rather than a system-wide or privileged Python environment.
- Avoid administrator or root installation unless it is demonstrably required.
- Document a controlled update process in which new package releases are reviewed and their hashes updated before users install them.
- Pin the dependency to a specifically reviewed release, for example:
