T08 · Insecure Dependencies
- Location
SKILL.md:56- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 56
Vulnerability Type: T08: Insecure Dependencies
Risk Level: MediumVulnerable Code Snippet:
bash clawhub install hai-agent-frameworkTechnical Analysis
The installation instruction retrieves
hai-agent-frameworkby package name without specifying an immutable version, release digest, commit identifier, or verified source. Consequently, the installed content is determined by the package registry at installation time and may differ from the content originally audited.The repository contains only
SKILL.md; the scripts and agent definitions advertised by the documentation are not present for local review. Users must therefore trust externally retrieved package content before executing the documented hook and memory-processing scripts.This finding does not establish that the named package is currently malicious. The vulnerability is the absence of dependency pinning and integrity verification, which creates supply-chain exposure if the package, publisher account, registry, or dependency-resolution process is compromised.
Attack Path
- An attacker compromises the package publisher account or relevant registry infrastructure, or otherwise causes the package name to resolve to attacker-controlled content.
- The attacker publishes a modified release under the same package name.
- A user follows the documented unpinned installation command.
- The installer retrieves the attacker-controlled release because no version or cryptographic digest is required.
- Malicious package hooks or subsequently invoked framework scripts execute with the permissions of the installing user or agent runtime.
Impact Assessment
Successful exploitation could permit arbitrary actions within the privileges granted to the package installer and runtime. Depending on the execution environment, this could include reading or modifying project files, acc ...[truncated 395 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin installation instructions to a specific, reviewed package version.
- Where supported, require an immutable cryptographic digest or signed release rather than relying on a mutable package name or tag.
- Replace the placeholder repository reference with the authoritative source URL and document the expected publisher identity.
- Publish checksums and signature-verification instructions through a trusted channel.
- Include the advertised scripts, hooks, and agent definitions in the reviewable project artifact, or link them to an immutable source revision.
- Review the complete dependency tree and lock transitive dependencies before release.
- Install and execute the framework with least privilege in an isolated environment, without unnecessary credentials or access to sensitive files.
- Disable automatic lifecycle scripts during installation unless they have been explicitly reviewed and are required.
