T08 · Insecure Dependencies
- Location
SKILL.md:158- Finding
Unpinned Related Skill Installation Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 158–164
Vulnerability Type: Unverified and unpinned third-party Skill installation
Risk Level: MediumVulnerable Code
markdown ## Related Skills Install with `clawhub install <slug>` if user confirms: - `cloud` - General cloud architecture and platform tradeoff guidance - `cloud-storage` - Object storage design, migration, and operations patterns - `payments` - Payment flow design, merchant risk checks, and launch discipline - `in-depth-research` - Broader market and source-comparison workflows - `market-research` - Competitive and market-level framing beyond product routingTechnical Analysis
The project recommends installing related Skills by mutable slug without specifying a trusted publisher, immutable version, integrity digest, or source-review procedure. User confirmation prevents silent installation, but it does not verify the provenance or integrity of the resolved package.
If a listed package is compromised, replaced, transferred to an untrusted publisher, or resolved from an unsafe source, the installed Skill may contain malicious instructions or executable components. Its effective capabilities depend on the host Agent and the permissions granted when that Skill is loaded.
Attack Path
- An attacker compromises, replaces, or gains control of one of the listed Skill slugs.
- A user receives the recommendation to install that related Skill.
- The user confirms installation, believing the slug identifies a trusted dependency.
- The Agent executes
clawhub install <slug>without an immutable version or integrity check. - The malicious or modified Skill is installed and subsequently loaded.
- Its instructions or bundled components may attempt to manipulate the Agent, access available data, invoke tools, or perform other actions within the Agent's granted permissions.
Impact Assessment
Successful exploitation could expose any files, tools, cre ...[truncated 483 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin each recommended Skill to an immutable, reviewed version.
- Identify and verify the expected publisher for every dependency.
- Require cryptographic integrity or signature verification before installation.
- Display the resolved package source, publisher, version, and permissions before requesting approval.
- Review downloaded Skill instructions and bundled scripts before activation.
- Reject unexpected publisher changes, mutable aliases, unsigned artifacts, and integrity mismatches.
- Prefer a trusted allowlist or lockfile containing verified package identifiers and hashes.
- Run third-party Skills with least privilege and isolate their filesystem, network, memory, and tool access.
