T08 · Insecure Dependencies
Warning
- Location
SKILL.md:42- Finding
Unpinned Installation from a Mutable Remote Repository
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 42-45
Vulnerability Type: Supply-chain risk caused by an unpinned remote Skill dependency
Risk Level: MediumVulnerable Code
markdown ## Installation Using OpenClaw CLI: ```bash openclaw install skill https://github.com/swimmingkiim/openclaw-skill-ai-news-oracletext ### Technical Analysis The documented installation command retrieves the Skill directly from a mutable GitHub repository without specifying a reviewed commit hash, immutable release artifact, checksum, or cryptographic signature. Consequently, the content installed by a user can differ from the artifact covered by this audit. This is a supply-chain weakness rather than evidence that the currently reviewed `SKILL.md` contains an active malicious payload. If the repository owner account, repository, release process, or referenced default branch is compromised, an attacker could replace the remote Skill with altered instructions or executable components. Users who subsequently follow the documented command would retrieve the changed content without an integrity check. The Skill's legitimate news aggregation functionality does not require installation from an unpinned source, so this risk exceeds the minimum trust necessary for distribution. ### Attack Path 1. An attacker compromises the GitHub maintainer account, repository, or another part of the repository publishing workflow. 2. The attacker modifies the repository's default branch to include malicious Skill instructions, scripts, or configuration. 3. A user executes the documented `openclaw install skill` command. 4. OpenClaw retrieves the repository's current mutable content rather than the version reviewed in this audit. 5. The altered Skill is installed and may influence the agent or execute code when loaded or invoked, depending on the malicious content and the permissions available to OpenClaw. ### Impact Assess ...[truncated 710 chars]- Remediation
View remediation
Remediation Suggestions
- Replace the mutable repository installation reference with an immutable, reviewed commit hash or versioned release.
- Publish signed release artifacts and require signature verification before installation.
- Provide a trusted checksum for the exact audited package and document how users must verify it.
- Protect the upstream repository with multi-factor authentication, branch protection, mandatory review, and restricted release permissions.
- Establish a reproducible release process so installed artifacts can be compared with reviewed source.
- Re-audit the Skill whenever the pinned version or dependency set changes.