T08 · Insecure Dependencies
- Location
SKILL.md:199- Finding
Unpinned Third-Party Skill Installation Commands
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 199–203
Vulnerability Type: Supply-chain risk from mutable, unverified dependencies
Risk Level: MediumVulnerable Code
markdown | resume-studio | Word/PDF resume | `npx clawhub@latest install resume-studio` | | resume-html | HTML resume | `npx clawhub@latest install resume-html` | | research-orchestrator | Industry research | `npx clawhub@latest install research-orchestrator` | | word-studio | Word report | `npx clawhub@latest install word-studio` | | pdf-studio | PDF report | `npx clawhub@latest install pdf-studio` |Technical Analysis
The documented integration commands invoke
npxwith the mutableclawhub@latestpackage reference and install five third-party Skills without fixed versions, integrity hashes, lockfiles, or publisher verification.Because
latestcan resolve to a different package release over time, the effective installation behavior may change after this Skill has been audited. The referenced Skills are also identified only by mutable names. If the npm package, distribution account, registry resolution, or any referenced Skill is compromised, users following these commands could retrieve and execute content that was not included in this audit.This is an insecure dependency and supply-chain pattern. The reviewed file does not prove that any current upstream package is malicious, but its installation guidance lacks controls that would make dependency retrieval reproducible and verifiable.
Attack Path
- An attacker compromises the publisher account, release process, or another distribution component for
clawhub, or gains control of a referenced Skill. - The attacker publishes a modified release selected by the mutable
latesttag or replaces the content associated with one of the referenced Skill names. - A user follows an installation command from
SKILL.md. npxretrieves and runs the package currently resolved asclawhub@latest. 5 ...[truncated 758 chars]
- An attacker compromises the publisher account, release process, or another distribution component for
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an exact, reviewed version, for exampleclawhub@X.Y.Z. - Pin exact versions or immutable identifiers for every referenced Skill.
- Verify downloaded artifacts using cryptographic integrity hashes or signed provenance metadata.
- Use lockfiles or an equivalent reproducible dependency manifest where supported.
- Document the expected publisher, package source, version, and checksum for each integration.
- Review each referenced Skill and its transitive dependencies before recommending installation.
- Configure installation tooling to reject unexpected registries, unsigned artifacts, and version drift.
- Update pinned versions only through a controlled review and security-testing process.
- Replace
