T08 · Insecure Dependencies
- Location
README.md:9- Finding
Mutable Third-Party Installation Sources Create a Skill Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 9–19
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code Snippet:
markdown > 📖 **Complete setup guide**: https://skillboss.co/skill.md ### Via ClawHub ```bash clawhub install modesty-data-analysisManual Installation
bash git clone https://github.com/ModestyRichards/data-analysis.git cp -r data-analysis ~/.openclaw/skills/data-analysistext ### Technical Analysis The installation documentation directs users to an external setup guide hosted on an unrelated domain and permits manual installation from a mutable Git repository reference. The Git command does not pin an immutable commit or verified release, and no checksum or signature verification is required before the downloaded content is copied into the active OpenClaw Skill directory. Consequently, the material installed by a user at a later date may differ from the package reviewed during this audit. Compromise of the external domain, GitHub account, repository, or default branch could allow altered Skill instructions or executable files to be distributed without changing the audited artifact. The README also uses inconsistent installation identifiers: `data-analysis` for one installation method and `modesty-data-analysis` for another. This ambiguity can increase the chance that users install a different or unintended package. No malicious payload, automatic download behavior, or automatic code execution was found in the audited project. Exploitation requires a user or automation system to follow the documented installation steps. ### Attack Path 1. An attacker compromises the external setup domain, GitHub repository, repository owner account, or another mutable upstream distribution source. 2. The attacker replaces or modifies the upstream Skill content with malicious instructions or executable files. 3. A user follows the RE ...[truncated 1237 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the external setup-guide dependency or place the complete installation documentation inside the audited repository.
- Pin manual installation to an immutable commit hash or cryptographically signed release tag rather than cloning the mutable default branch.
- Publish SHA-256 checksums or signed manifests for release artifacts and require verification before installation.
- Use one canonical Skill identifier consistently across OpenClaw, ClawHub, repository, and manual installation instructions.
- Prefer a trusted registry release that is explicitly associated with the reviewed project version.
- Document the expected repository owner, release version, commit hash, and verification procedure.
- Avoid copying unverified repository contents directly into an active Skill directory. Download and validate them in a staging location first.
