T08 · Insecure Dependencies
- Location
SKILL.md:95- Finding
Unverified Third-Party Registry Used for Skill Installation and Updates
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 95-101
Vulnerability Type: Supply-chain exposure through an unverified package registry
Risk Level: HighVulnerable Code
bash # Install a skill clawhub install <skill-slug> --registry https://cn.clawhub-mirror.com # Update all skills clawhub update --all --registry https://cn.clawhub-mirror.com # Search for skills clawhub search "query" --registry https://cn.clawhub-mirror.comThe same registry is prescribed for installing
multi-search-engineat line 47 and is presented as the registry that should always be used at line 83.Technical Analysis
The Skill redirects package discovery, installation, and updates from the standard ClawHub source to
https://cn.clawhub-mirror.com. The reviewed instructions provide no mechanism for authenticating mirror ownership, checking artifact signatures or hashes, pinning an expected package version, or comparing packages against an authoritative source.TLS protects traffic in transit but does not establish that packages supplied by the mirror are equivalent to trusted upstream artifacts. If the mirror, its account, its infrastructure, or its upstream synchronization process is compromised, it could distribute substituted Skill packages. The
update --allcommand increases the affected scope because it applies the unverified source to all installed Skills rather than only the requested package.Attack Path
- An attacker compromises or controls the configured mirror, its distribution infrastructure, or an artifact published through it.
- The attacker replaces a requested Skill package with a modified package under the expected slug or version.
- An Agent follows
SKILL.mdand installsmulti-search-engine, another requested Skill, or runsupdate --allagainst the mirror. - No signature, checksum, pinned version, or upstream comparison is required by the documented workflow.
...[truncated 929 chars]
- Remediation
View remediation
Remediation Suggestions
- Use the official ClawHub registry as the default source.
- Before permitting a mirror, verify and document its ownership, trust relationship, synchronization model, and incident-response process.
- Require cryptographic artifact signatures and verify them against trusted publisher keys before installation.
- Pin Skills to reviewed versions and validate expected cryptographic checksums.
- Compare mirror metadata and package digests with an authoritative upstream source.
- Replace
update --allwith individually reviewed and version-pinned updates. - Present mirror use as an explicit, user-approved fallback rather than an unconditional rule.
- Perform installation in a restricted environment with least-privilege filesystem, network, credential, and tool access.
