T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:159
- Finding
- Unpinned Third-Party Skill Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 159-166 **Vulnerability Type**: Unverified and unpinned third-party Skill dependencies **Risk Level**: Medium **Vulnerable Code:** ```markdown ## Related Skills Install with `clawhub install <slug>` if user confirms: - `dutch` — Dutch language learning and practice - `travel` — Travel planning and trip organization - `career` — Career development and job search - `freelance` — Freelancing guidance and contracts - `plan` — General planning and goal setting ``` ### Technical Analysis The Skill recommends installing third-party Skills through mutable package slugs. It does not pin versions, identify trusted publishers, specify integrity hashes or signatures, or require inspection of the resolved package before installation. User confirmation reduces the likelihood of an unexpected installation, but it does not verify dependency integrity. If a referenced slug is compromised, transferred, replaced, or resolved from an unsafe source, the installed package could contain hostile instructions or executable components that were not present during this audit. ### Attack Path 1. An attacker compromises, replaces, or gains control of one of the referenced Skill slugs. 2. The Utrecht Skill recommends that dependency for a related user request. 3. The user confirms installation, believing the recommendation implies the dependency is trusted. 4. The Agent executes `clawhub install <slug>` without a pinned version or integrity verification. 5. The malicious dependency is loaded and may introduce hostile instructions or executable behavior according to the permissions available to the Skill runtime. ### Impact Assessment The immediate file does not itself execute a malicious payload. The potential impact depends on the installed dependency and the permissions granted by the Agent platform. A compromised dependency could alter Agent behavior, expose d ...[truncated 391 chars]
- Remediation
- ## Remediation Suggestions 1. Pin each recommended dependency to a reviewed immutable version rather than installing by mutable slug alone. 2. Record and verify the dependency publisher, package source, and cryptographic checksum or signature. 3. Display the resolved package name, version, publisher, requested permissions, and source before asking for user approval. 4. Require security review of dependency contents, including instruction files and executable scripts, before installation. 5. Apply least-privilege sandboxing to installed Skills and deny filesystem, network, credential, and command-execution access unless explicitly required. 6. Maintain an allowlist of approved dependency versions and alert users if the resolved artifact differs from the reviewed version. 7. Prefer describing related capabilities without issuing an installation command when dependency integrity cannot be established.
