T08 · Insecure Dependencies
- Location
SKILL.md:55- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 55-58
Vulnerability Type: Unpinned external executable dependency
Risk Level: MediumVulnerable Code Snippet
bash pip install hermes-guard hermes-guard auditTechnical Analysis
The installation command retrieves the latest available
hermes-guardpackage from the default Python Package Index without pinning a reviewed version or verifying an integrity hash. The subsequently invoked console command executes code supplied by that external package.The implementation of the dependency is not included in the audited artifact. Consequently, its behavior cannot be verified, and the code users receive may change independently after this skill has been reviewed. A compromised publisher account, malicious future release, package-index compromise, or dependency-confusion condition could introduce attacker-controlled code.
This finding does not establish that the current package is malicious. It identifies an unsafe supply-chain trust model in the documented installation process.
Attack Path
- An attacker compromises the package publisher, package distribution channel, or a transitive dependency.
- The attacker publishes a malicious release under the package name used by the documentation.
- A user follows the documented
pip install hermes-guardcommand. - Because no version or hash is specified, pip retrieves the attacker-controlled release.
- Package installation hooks, imported modules, or the subsequent
hermes-guard auditcommand execute the malicious code. - The code runs with the privileges of the user or service account performing the installation and audit.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on that account's permissions, this may expose project files, environment variables, API credentials, Agent configuration, and oth ...[truncated 223 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the package to a specifically reviewed version rather than installing the latest release.
- Publish a lock file containing exact versions for all transitive dependencies.
- Require cryptographic hashes by using a hash-locked requirements file and pip's
--require-hashesoption. - Document the authoritative package repository and verify that package ownership matches the linked source repository.
- Build packages in a controlled pipeline and verify signed release artifacts where supported.
- Run the package inside an isolated environment with minimal filesystem, network, and credential access.
- Include the executable implementation in the review scope so its actual behavior can be audited before deployment.
