T08 · Insecure Dependencies
- Location
SKILL.md:231- Finding
Unpinned Third-Party Package and Skill Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:231-254
Vulnerability Type: Supply-chain risk from mutable, unverified dependencies
Risk Level: MediumThe quick-start guide instructs users to execute the latest available version of a registry package and use it to install four additional Skills:
bash # Install MCP tools npx clawhub@latest install mcp-tools # Configure academic data sources openclaw mcp add academic --connector arxiv --connector semantic-scholar # Install Stata Skill npx clawhub@latest install stata-skill # Translate using Python stata-to-python --input paper.do --output paper.py # Install the review-response assistant npx clawhub@latest install review-response # Convert a paper to PPT npx clawhub@latest install paper-slide-deckTechnical Analysis
The four installation commands invoke
npx clawhub@latest. The@latesttag is mutable and does not identify the exact package version or integrity hash reviewed by the author.npxmay download and execute registry-hosted package code as the current user. The invoked installer then retrieves additional Skills whose versions, publishers, contents, integrity values, and required permissions are not specified in this artifact.Consequently, the effective code and instructions executed by users can change after this Skill has been reviewed. A compromised registry account, package takeover, malicious future release, or compromised transitive dependency could introduce hostile behavior without requiring any modification to
SKILL.md.The MCP configuration and
stata-to-pythoncommands are included in the complete workflow snippet for context. The confirmed issue is specifically the use of mutable@latestinstallation commands and the absence of dependency verification.Attack Path
- An attacker compromises the
clawhubpackage, one of the named Skills, or a relevant dependency or publisher account. - The at ...[truncated 1294 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version. - Pin each installed Skill to a specific immutable version or commit identifier where the tooling supports it.
- Verify package integrity using registry checksums, lockfiles, signatures, provenance attestations, or trusted release hashes.
- Document the expected publisher, canonical repository, reviewed version, required permissions, and relevant integrity value for every dependency.
- Review the package, its lifecycle scripts, transitive dependencies, and each downloaded Skill before execution.
- Disable or avoid unnecessary installation scripts and execute installation in a sandbox or least-privilege environment.
- Add a confirmation step that displays the resolved version and source before downloading or executing it.
- Maintain an allowlist of approved packages and Skills, monitor them for ownership or release changes, and document rollback and removal procedures.
- Replace
