T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:31
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash pip install ollama-herd # PyPI: https://pypi.org/project/ollama-herd/Technical Analysis
The Skill directs users to install
ollama-herdfrom PyPI without specifying an exact version or verifying an integrity hash. Consequently, the package resolved at installation time may differ from the version that existed when the Skill was reviewed.The package provides the
herdandherd-nodeexecutables used by the Skill, but their implementation is not included in this project. The audit therefore cannot verify the behavior of the code that users are instructed to install and run. If the package publisher, PyPI account, release process, or transitive dependency chain is compromised, an attacker could distribute modified executable code under this installation command.Attack Path
- An attacker compromises the
ollama-herdpublishing account, release pipeline, source distribution, wheel, or a dependency resolved during installation. - The attacker publishes a malicious release that remains compatible with the unpinned package name.
- A user follows the documented
pip install ollama-herdinstruction. pipresolves and installs the attacker-controlled release or dependency.- Malicious behavior can occur during package installation if the selected package format invokes build code, or when the user subsequently executes
herdorherd-nodeas instructed. - The payload runs with the privileges of the user performing the installation or launching the installed commands.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing or invoking user's account. The resulting code could access files, credentials, environment variables, local network services, GPU resources, and other ...[truncated 405 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
ollama-herdto an exact, reviewed version rather than installing the latest available release. - Publish expected hashes for the approved wheel or source archive and require hash verification, such as through a locked requirements file used with
pip install --require-hashes. - Pin and audit all transitive dependencies using a reproducible lockfile.
- Prefer a prebuilt, reviewed wheel to avoid executing arbitrary source-build logic during installation.
- Install the package in an isolated virtual environment under an unprivileged user account.
- Document the trusted package source, release-signing or provenance-verification process, and the reviewed version.
- Re-audit the installed package and its dependencies before recommending any updated release.
- Pin
