T08 · Insecure Dependencies
- Location
SKILL.md:29- Finding
Unpinned Third-Party Packages Are Installed and Immediately Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29-31
Vulnerability Type: Unpinned and unverified third-party dependencies
Risk Level: MediumVulnerable Code
bash pip install ollama-herd herd # start the transcription router (port 11435) herd-node # start on each transcription device uv tool install "mlx-qwen3-asr[serve]" --python 3.14 # install speech-to-text modelTechnical Analysis
The setup instructions install the latest available versions of
ollama-herd,mlx-qwen3-asr, and their transitive dependencies without version constraints, package hashes, a lock file, or signature verification. The instructions then immediately execute the installedherdandherd-nodeentry points.Package installation can execute package build or installation logic, while the installed entry points execute package-controlled code directly. Consequently, the effective code run by users may change after this skill has been reviewed. A compromised package release, compromised maintainer account, or malicious transitive dependency could therefore introduce arbitrary code.
The documented package and repository names are consistent with the skill's declared functionality, and the audit found no evidence that the named packages are intentionally malicious. This finding concerns the unsafe dependency acquisition and execution model rather than a confirmed malicious payload.
Attack Path
- An attacker compromises a named package, one of its transitive dependencies, or the relevant package-publishing account.
- The attacker publishes a malicious release that still satisfies the unconstrained installation commands.
- A user follows the instructions and runs
pip install ollama-herdor the unpinneduv tool installcommand. - The package manager retrieves and installs the attacker-controlled release.
- Malicious code may execute during installation or when the use ...[truncated 787 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every directly installed package to a reviewed, exact version, for example
ollama-herd==X.Y.Z. - Pin transitive dependencies through a reviewed lock file or constraints file.
- Require cryptographic package hashes where supported, such as a hash-locked requirements file installed with
pip --require-hashes. - Publish and verify expected package provenance, repository ownership, release signatures, and checksums.
- Install packages inside an isolated virtual environment or dedicated
uvenvironment rather than the user's global Python environment. - Separate installation from execution so users can inspect the resolved dependency set before launching
herdorherd-node. - Recommend running the router and worker with a dedicated, non-administrative account that has access only to required audio and application directories.
- Document the network interfaces on which the service listens and default to loopback unless fleet access is explicitly required.
- Pin every directly installed package to a reviewed, exact version, for example
