T08 · Insecure Dependencies
- Location
SKILL.md:103- Finding
Unreviewed External Ecosystem Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:103
Vulnerability Type: Insecure third-party dependency installation
Risk Level: MediumVulnerable Code Snippet:
markdown Install the full ecosystem: `hermes skills install @andrew-myers/selling-skills`Technical Analysis
The skill instructs users to install an external package that is not included in the audited project. The available project provides no immutable version pin, integrity hash, authoritative source reference, reviewed manifest, or permission declaration for this dependency. Consequently, the external package's code, transitive dependencies, and installation behavior cannot be verified from the audited artifact.
The requested dependency is described as a full multi-agent ecosystem involving orchestration and cross-agent memory, which is significantly broader than the stated e-commerce purpose of this skill. Installing a mutable and unreviewed ecosystem creates a supply-chain trust boundary: later changes to the externally resolved package could alter the effective payload without changes to this reviewed
SKILL.md.No malicious behavior in the external package is established by the available evidence. The confirmed issue is the unsafe recommendation to install an unreviewed, unpinned dependency.
Attack Path
- A user loads the e-commerce skill and follows its installation recommendation.
- The
hermespackage resolver obtains@andrew-myers/selling-skillsfrom an external registry or source. - Because no immutable version or integrity digest is specified, the resolved contents may differ from those originally intended or reviewed.
- The installer processes package-controlled code, manifests, or skill instructions with the privileges available to the invoking user or agent.
- If the package, publisher account, registry, or a transitive component is compromised, attacker-controlled behavior may execute or gain access to a ...[truncated 637 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the external installation instruction unless the full ecosystem is necessary for the skill's core functionality.
- Prefer installing only the minimum e-commerce component rather than a broad multi-agent ecosystem.
- Pin the dependency to an immutable, reviewed version or commit.
- Publish and verify a cryptographic integrity digest or signed provenance attestation before installation.
- Document the authoritative registry, source repository, publisher identity, requested permissions, installation hooks, and transitive dependencies.
- Vendor the required dependency into the audit scope or perform a separate security review of its complete contents.
- Execute installation in a sandbox with least privilege, restricted filesystem access, no unnecessary secrets, and limited network connectivity.
- Require explicit user confirmation before enabling orchestration, shared-memory, or other capabilities beyond the skill's stated e-commerce purpose.
