T08 · Insecure Dependencies
- Location
SKILL.md:72- Finding
Unpinned ERC-8004 Skill Installation Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 72
Vulnerability Type: Unpinned third-party skill installation
Risk Level: MediumComplete Code Snippet:
markdown - To register onchain and link your identity: `clawhub install erc-8004`Technical Analysis
The documentation instructs users or agents to install the externally maintained
erc-8004skill without specifying an immutable version, content digest, trusted publisher identity, or verification procedure. The effective installed content can therefore differ from the content available when this project was audited.This represents an insecure dependency boundary because the associated workflow concerns on-chain identity and token incentives. If the registry entry, publisher account, distribution infrastructure, or mutable latest release were compromised, an attacker could distribute altered instructions or executable components under the expected skill name.
No evidence in this project establishes that the current
erc-8004skill is malicious. The vulnerability is the absence of controls ensuring that future installations retrieve the reviewed artifact.Attack Path
- An attacker compromises the dependency publisher, registry entry, or distribution channel for
erc-8004, or substitutes an untrusted package with the expected name. - The attacker publishes a modified version containing malicious instructions or code.
- A user or agent follows
SKILL.mdand runsclawhub install erc-8004without validating a version, digest, or publisher. - The mutable dependency is installed and subsequently invoked.
- The dependency attempts to abuse whatever API credentials, wallet access, tools, files, or network permissions are available to its runtime.
Impact Assessment
Exploitation could affect the privileges granted to the installed skill, potentially including access to agent-visible credentials, authenticated service ope ...[truncated 282 chars]
- An attacker compromises the dependency publisher, registry entry, or distribution channel for
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an immutable, reviewed version rather than installing the mutable latest release.
- Require verification of a cryptographic content digest or signed release manifest before installation.
- Document the expected publisher identity and authoritative registry source.
- Audit the complete dependency contents, including scripts and transitive dependencies, before use.
- Run the skill with least privilege and isolate wallet access, API credentials, filesystem access, and network access.
- Require explicit human approval for on-chain registration, signing, token transfer, or other irreversible operations.
- Maintain an allowlist of approved skill versions and periodically review them for publisher or checksum changes.
