T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned Third-Party Executable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:23-27
Vulnerability Type: Unpinned third-party package installation
Risk Level: MediumVulnerable Code
bash pip install hermescheck hermescheck /path/to/hermes-agentThe same unsafe installation pattern also appears at
README.md:82-90andreferences/code-patterns.md:9-12.Technical Analysis
The Skill directs users to install
hermescheckfrom the default Python package index without specifying a version or verifying a cryptographic hash. The executable implementation is not included in this artifact, so its behavior cannot be validated by reviewing the Skill package.Because the dependency is mutable, the code ultimately executed may differ from the version that existed when the Skill was reviewed. Compromise of the package publisher account, package-index distribution path, or a future release could introduce malicious behavior. Running a repository scanner necessarily gives the installed package read access to the target repository and the ambient privileges of the invoking user.
The installation is relevant to the declared auditing function, but using an unpinned and unverified executable dependency provides more supply-chain trust than is minimally necessary.
The static pre-scan’s other alerts were not confirmed as vulnerabilities:
README.md:31is a GitHub Actions hyperlink with a Shields.io badge image; it does not download or execute a file.- Network and sensitive-data expressions in
references/code-patterns.mdare inert regular-expression examples used to describe scanner detections. They do not transmit data. - No embedded scripts, credential-harvesting logic, persistence installation, prompt hijacking, or active network-exfiltration implementation was found in the reviewed artifact.
Attack Path
- An attacker compromises the
hermescheckpackage publisher account or causes a malicious future version to be distributed through the configured Python p ...[truncated 1218 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin
hermescheckto a specifically reviewed version rather than installing the latest available release:bash python -m pip install "hermescheck==X.Y.Z" -
Publish and require cryptographic hashes through a locked requirements file:
text hermescheck==X.Y.Z --hash=sha256:REVIEWED_PACKAGE_HASHInstall it with:
bash python -m pip install --require-hashes -r requirements-hermescheck.txt -
Record the reviewed package version, source repository commit, wheel hash, and expected publisher identity in the Skill documentation.
-
Prefer a wheel built by a trusted, reproducible CI process. Avoid source-distribution installation where build hooks could execute unreviewed code.
-
Run the scanner in an isolated environment with:
- Read-only access limited to the intended target repository
- Network access disabled during scanning
- No inherited API keys or unrelated credentials
- A dedicated unprivileged account or disposable container
- Output write access limited to a designated report directory
-
Update every occurrence of the installation command in
SKILL.md,README.md, andreferences/code-patterns.mdso users are not directed toward the unpinned alternative.
-
