T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Installation of an Unaudited External Skill
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 10–14
Vulnerability Type: Unpinned third-party Skill dependency
Risk Level: MediumComplete Code Snippet
markdown This is a reserved name. Install the main skill instead:clawhub install contentclaw
text Technical Analysis
The project is a placeholder that directs users to install the external
contentclawSkill by mutable package name. The command does not specify an immutable version, cryptographic digest, verified source repository, or publisher identity.The downstream Skill is not included in this repository and was therefore outside the audit scope. Its effective instructions and executable components may change independently after this artifact has been reviewed. This creates a supply-chain trust boundary in which users are encouraged to install and trust unreviewed content.
The audited file does not itself retrieve or execute a remote payload, and there is no evidence that the referenced package is malicious. The issue is the unsafe, unpinned dependency installation pattern.
Attack Path
- An attacker compromises the registry account, publication process, or distribution entry associated with
contentclaw, or otherwise causes a malicious release to be served under that mutable name. - A user follows the documented
clawhub install contentclawcommand. - The package manager resolves the name to the attacker-controlled or unexpectedly modified release without checking an expected version or digest.
- The downstream Skill is installed and may execute with whatever tools, credentials, filesystem access, or network permissions the user or Agent grants it.
- Malicious instructions or code in that package could then act within those granted privileges.
Impact Assessment
Successful exploitation could expose the permissions available to the installed Skill, potentially including Agent tools, local files, network access, and service credentials. The ...[truncated 424 chars]
- An attacker compromises the registry account, publication process, or distribution entry associated with
- Remediation
View remediation
Remediation Suggestions
- Pin the downstream Skill to a reviewed, immutable version and cryptographic digest rather than installing solely by package name.
- Publish the canonical source repository, verified publisher identity, release signature, and expected digest.
- Add package-manager integrity and signature verification to the installation procedure.
- Document the downstream Skill's required permissions, external endpoints, credential usage, and data-handling behavior before installation.
- Require explicit user review and confirmation before installing or enabling the external Skill.
- Re-audit each new dependency release before updating the pinned version.
- Apply least privilege by withholding filesystem, network, publishing, and credential access unless each capability is necessary and explicitly authorized.
