T08 · Insecure Dependencies
- Location
README.md:23- Finding
Mutable Placeholder Repository Used as the Installation Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 23-26
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediumtext ## Installation In Kimi Claw, enter: Install this skill: https://github.com/yourname/37c-sootherTechnical Analysis
The documented installation procedure directs users to retrieve the Skill from a GitHub repository containing the placeholder owner
yourname. The source is not tied to a verified publisher, immutable commit, signed release, checksum, or other integrity control.Because a repository reference normally resolves to mutable content, the files installed by a user could differ from the two files reviewed in this audit. An operator controlling the referenced namespace could replace the benign Skill instructions with malicious instructions or executable components after review.
The audited project itself does not contain code that automatically downloads or executes this repository. The vulnerability is therefore limited to the documented supply-chain installation path and depends on a user or installer following that instruction.
Attack Path
- A user follows the installation command in
README.md. - The installer resolves the mutable GitHub repository rather than a reviewed, immutable revision.
- An attacker controls, compromises, or substitutes the referenced repository.
- The attacker publishes altered Skill files, malicious instructions, or executable components.
- The installer retrieves and loads that unaudited content.
- The malicious content operates with whatever tools and permissions the hosting agent grants to installed Skills.
Impact Assessment
Successful exploitation could cause users to install content that was not included in the audited project. The resulting impact would depend on the capabilities granted by the host environment. It could include manipulation of agent behavior or, if an altered package introduced ...[truncated 451 chars]
- A user follows the installation command in
- Remediation
View remediation
Remediation Suggestions
- Replace the placeholder URL with the verified canonical repository owned by the actual publisher.
- Pin installation to an immutable commit hash or a cryptographically signed release rather than a mutable branch.
- Publish a SHA-256 checksum or signed manifest for the reviewed package and require verification before installation.
- Document the expected package contents so users can confirm that no unexpected scripts or configuration files were added.
- Protect the source repository with multi-factor authentication, restricted release permissions, branch protection, and mandatory review.
- Configure the installer to reject unresolved placeholders and warn users when a Skill is fetched from an unverified or mutable source.
