T08 · Insecure Dependencies
- Location
README.md:51- Finding
Unpinned Skill Installation from a Mutable Remote Repository
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 51
Vulnerability Type: Unpinned third-party Skill supply chain
Risk Level: Mediumbash git clone https://github.com/LeonFJR/opc-skills.git ~/.claude/skills/opc-skillsTechnical Analysis
The documented installation command clones the current default branch of a remote repository without pinning it to a reviewed commit or signed release and without performing an integrity check. The command also installs the complete Skill suite into the Agent's Skill directory rather than limiting installation to this audited Skill.
Consequently, the content installed by this command can differ from the content reviewed during this audit. If the repository, its maintainer account, or its release process is compromised, an attacker could add malicious Skill instructions or executable scripts to the default branch. Placing such content in
~/.claude/skills/may cause it to be loaded or invoked in later Agent sessions.The reviewed project itself contains no malicious runtime code, remote payload execution, credential collection, persistence mechanism, or privilege-escalation behavior. The risk arises specifically from the mutable and unverified installation source documented in the README.
Attack Path
- An attacker compromises the remote repository, a maintainer account, or another component of its publishing process.
- The attacker modifies the repository's default branch to include hostile Skill instructions or executable scripts.
- A user follows the documented
git clonecommand. - The command installs the attacker's modified repository, including potentially unrelated Skills, into
~/.claude/skills/opc-skills. - The Agent subsequently loads or invokes the malicious Skill content.
- The malicious content can influence Agent behavior or execute code with the permissions of the user running the Agent, subject to the Agent's tool and sandbox restr ...[truncated 700 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin installation instructions to a specific, reviewed commit hash or immutable release artifact rather than the mutable default branch.
- Publish a SHA-256 checksum or cryptographic signature for each release and require users to verify it before installation.
- Provide an installation procedure that copies only
opc-cashflow-managerinstead of cloning the entire Skill suite into the Agent's Skill directory. - Use signed Git tags or release attestations and document how users can verify the maintainer signature.
- Review installed Skill files before enabling them, particularly instruction files and executable content under
scripts/. - Perform updates explicitly and pin each update to a newly reviewed version rather than automatically tracking the remote default branch.
A hardened installation flow should resemble:
bash git clone https://github.com/LeonFJR/opc-skills.git /tmp/opc-skills cd /tmp/opc-skills git checkout --detach <reviewed-commit-hash> # Verify the published checksum or signature here. cp -r opc-cashflow-manager ~/.claude/skills/opc-cashflow-manager
