T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned Third-Party Package Is Installed and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 25-27
Vulnerability Type: Unpinned executable dependency
Risk Level: Mediumbash pip install ollama-herd # install private AI router herd # start private AI router (port 11435) herd-node # run on each device — private AI nodes discover each otherTechnical Analysis
The setup instructions install
ollama-herdfrom the package index without pinning an exact version or verifying an integrity hash. They then instruct the user to execute the package-providedherdandherd-nodecommands.Python packages can execute installation or runtime code with the privileges of the invoking user. Because the dependency's source code is not included in the audited project, its networking, telemetry, file-access, and model-download behavior cannot be verified from this artifact. An unrestricted installation may also resolve to a future package release that differs from the version originally reviewed.
Installing a third-party component is necessary for the documented functionality, but accepting any available version without cryptographic verification exceeds the minimum supply-chain trust needed for a reproducible installation.
Attack Path
- An attacker compromises the package maintainer account, package repository, release pipeline, or another component in the dependency chain.
- The attacker publishes a malicious release under the expected
ollama-herdpackage name. - A user follows the documented
pip install ollama-herdinstruction, andpipresolves the malicious release because no version or hash is specified. - Malicious code may run during installation or when the user invokes
herdorherd-node. - The payload executes with the user's privileges and can access resources available to that account.
This is a conditional supply-chain exploitation path; the audit found no evidence that the c ...[truncated 669 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
ollama-herdto a specific, reviewed version rather than allowing unrestricted package resolution. - Publish a lock file or requirements file containing cryptographic hashes and instruct users to install with hash enforcement, such as
pip install --require-hashes -r requirements.txt. - Document the authoritative package index and upstream source repository so users can verify package provenance.
- Sign releases or publish verifiable attestations and checksums for distributed artifacts.
- Recommend installation in a dedicated virtual environment or other isolated, non-administrative environment.
- Review the pinned package and its transitive dependencies for installation hooks, external network access, telemetry, sensitive-file access, and unsafe command execution before recommending it.
- Avoid instructing users to run installation or service commands with elevated privileges unless a narrowly scoped privilege is demonstrably required.
- Pin
