T08 · Insecure Dependencies
- Location
SKILL.md:59- Finding
Unpinned Third-Party Skills Create a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59-72
Vulnerability Type: Unpinned and unaudited third-party dependencies
Risk Level: Highpowershell py -m clawhub install ai-refactoring-assistant py -m clawhub install coding-agent py -m clawhub install gh-issues py -m clawhub install api-dev py -m clawhub install academic-writing-refiner py -m clawhub install feishu-doc py -m clawhub install healthcheck py -m clawhub install cronTechnical Analysis
The installation instructions retrieve eight third-party Skills by package name without specifying exact versions, immutable content digests, trusted publishers, or integrity checks. Consequently, the installed content depends on the mutable state of the package registry at installation time.
None of these dependencies are included in the audited artifact, so their code, permissions, transitive dependencies, and runtime behavior cannot be verified through this project. A registry compromise, publisher-account compromise, malicious package update, package-name reassignment, or dependency-confusion event could cause different and potentially malicious content to be installed under a documented name.
This is particularly sensitive because the advertised Skills interact with source code, GitHub issues, documentation platforms, health checks, and scheduled operations. Such integrations may receive repository credentials, API tokens, source code, or access to deployment infrastructure.
Attack Path
- An attacker compromises the publisher account or registry entry for one of the named Skills, or publishes a malicious replacement under a confusing or reassigned name.
- The attacker releases a malicious package version containing credential theft, unauthorized tool calls, or destructive behavior.
- A user follows the documented installation command without specifying a trusted version or digest.
- The package manager resolves and ins ...[truncated 977 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every Skill to an exact, reviewed version or, preferably, an immutable content digest.
- Document the expected registry origin and verified publisher identity for each dependency.
- Require cryptographic signature and checksum verification before installation.
- Maintain a lock file recording resolved versions, digests, and transitive dependencies.
- Review third-party Skill contents and permission requirements before approving updates.
- Run installed Skills in a sandbox with least-privilege filesystem, network, tool, and credential access.
- Expose repository and service credentials only when needed, using narrowly scoped and short-lived tokens.
- Add automated dependency monitoring and require security review for lock-file changes.
