T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 31
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash pip install ollama-herd # install the local LLM routerTechnical Analysis
The installation instruction retrieves and installs the latest available release of the
ollama-herdpackage without a version constraint or integrity hash. Python package installation may execute package-controlled build or installation logic. Subsequent execution of the installedherdandherd-nodecommands also runs code supplied by the package and its dependencies.Although the Skill identifies the intended PyPI project and source repository, it does not pin a reviewed version, verify an artifact hash, provide a lock file, or constrain transitive dependencies. Consequently, the code installed by users can differ from the code reviewed when this Skill was published. A compromised package-maintainer account, malicious future release, altered distribution artifact, or compromised transitive dependency could exploit this supply-chain boundary.
The audited Skill does not itself contain evidence that
ollama-herdis malicious. This finding concerns the unsafe dependency acquisition practice and the resulting exposure to mutable third-party code.Attack Path
- An attacker compromises the package publisher, distribution channel, or a transitive dependency and publishes a malicious release.
- A user follows the Skill instruction and runs
pip install ollama-herd. - Because no version or hash is specified,
pipresolves and downloads the attacker-controlled release or dependency. - Malicious package logic may execute during installation, depending on the selected distribution and build process.
- The user subsequently runs
herdorherd-node, executing the installed attacker-controlled runtime code.
Impact Assessment
Exploitat ...[truncated 675 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
ollama-herdto a specific version that has undergone security review. - Publish cryptographic hashes for the approved distribution artifacts and require hash verification, such as through a locked requirements file used with
pip install --require-hashes. - Pin and review transitive dependencies where feasible, using a reproducible lock file.
- Recommend installation into a dedicated virtual environment rather than the system Python environment.
- Advise users not to install or run the package with root or administrator privileges.
- Document how users can verify package provenance and compare the distributed artifact against the referenced source repository.
- Establish a controlled update process so new releases are reviewed before changing the pinned version and hashes.
- Pin
