T08 · Insecure Dependencies
Warning
- Location
README.md:116- Finding
Skill Installation Uses a Mutable Remote Repository
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 116-120
Vulnerability Type: Mutable remote dependency without commit or integrity pinning
Risk Level: Mediumbash ### Install ```bash # Claude Code users claude install-skill https://github.com/dingtom336-gif/outfit-video/tree/main/skills/viral-video-replicatortext ### Technical Analysis The documented installation command retrieves the Skill from a mutable GitHub branch rather than a reviewed commit, immutable release artifact, or cryptographically verified package. Consequently, the effective Skill content installed by a user can change after this audit without any change to the command. If the repository owner account, repository, or upstream branch is compromised, an attacker could replace the audited instructions with malicious Skill text or executable resources. The installer would then retrieve the modified version while the command continued to appear legitimate. This is a supply-chain weakness rather than evidence that the currently audited repository contains a malicious payload. ### Attack Path 1. An attacker compromises the upstream GitHub account, repository, or publishing workflow. 2. The attacker modifies the referenced Skill directory on the mutable branch. 3. A user runs the documented `claude install-skill` command. 4. The installer retrieves the modified, unaudited content. 5. When loaded, the modified Skill can issue malicious instructions or invoke available tools under the Agent's granted permissions. ### Impact Assessment The potential scope is limited by the privileges granted to the Agent and Skill installer. In a tool-enabled environment, a compromised Skill could access files available to the Agent, make network requests, expose conversation data, or execute commands permitted by the host. It would not inherently obtain operating-system privileges beyond those of the invoking user.- Remediation
View remediation
Remediation Suggestions
- Replace the mutable branch URL with an immutable, reviewed commit reference or signed release tag.
- Publish checksums or signed provenance for release artifacts.
- Document the exact reviewed revision in the installation instructions.
- Require users or the installer to verify artifact integrity before enabling the Skill.
- Establish a release process that prevents tags from being moved or overwritten.