T08 · Insecure Dependencies
- Location
SKILL.md:71- Finding
Unpinned Automatic Skill Update Creates a Mutable Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 71
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
bash clawhub update --skill academic-researchThe surrounding instruction requires this update to run weekly to synchronize the latest research methodology.
Technical Analysis
The Skill instructs the agent to periodically update the
academic-researchSkill without specifying an immutable version, trusted commit, integrity hash, signature requirement, change-review process, or approval gate. Consequently, the effective dependency can change after this package has been audited.If the upstream Skill, publisher account, distribution service, or update channel is compromised, a later update could introduce unauthorized instructions or executable behavior. The reviewed project does not itself contain a malicious payload, and exploitation depends on the behavior of the external update mechanism and subsequently retrieved content.
Attack Path
- An attacker compromises the upstream
academic-researchSkill, its publisher account, or the distribution channel. - The attacker publishes a modified release containing malicious instructions or references to malicious executable content.
- The weekly instruction invokes
clawhub update --skill academic-research. - Because no immutable version, integrity verification, or manual approval is required, the altered release is installed or synchronized.
- A later agent session loads or invokes the updated Skill.
- The malicious content then operates with the tools and permissions available to that agent session.
Impact Assessment
Successful exploitation could modify future agent behavior and potentially cause unauthorized tool calls, data access, network requests, or command execution if those capabilities are granted to the updated Skill. The attainable privileges are limited to those of the accou ...[truncated 265 chars]
- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
- Replace automatic latest-version updates with an explicitly pinned, audited version or immutable commit identifier.
- Verify downloaded artifacts using a trusted cryptographic signature and a pinned checksum before installation.
- Restrict updates to an authenticated, allowlisted registry and verify the publisher identity.
- Download updates into a staging environment rather than activating them immediately.
- Review instruction, script, permission, and dependency changes before promotion to production.
- Require explicit human approval for every update and record the approver, version, checksum, and review result.
- Run updated Skills with least privilege, limiting filesystem, network, credential, and command-execution access.
- Maintain a known-good version and a documented rollback procedure.
