T08 · Insecure Dependencies
- Location
README.md:26- Finding
Unpinned Remote Repository Installed into a Trusted Skills Directory
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 26-31
Vulnerability Type: Supply-chain risk from an unpinned remote dependency
Risk Level: MediumVulnerable Code Snippet:
bash mkdir -p ~/.codex/skills git clone https://github.com/ramensushi2026/openclaw-cli-skill.git ~/.codex/skills/openclaw-cliTechnical Analysis
The documented installation procedure clones the repository's mutable default branch directly into
~/.codex/skills, a directory from which Codex skills may be loaded and trusted. It does not pin an immutable commit, require a signed release, or verify a checksum or cryptographic signature.Consequently, the content installed by this command can differ from the version reviewed during this audit. This does not demonstrate that the current repository is malicious; however, it creates an unsafe supply-chain path. A compromise of the repository owner, hosting account, or default branch could introduce modified instructions, configuration, or executable components into future installations without an independent integrity check.
Attack Path
- An attacker compromises the upstream repository account or otherwise obtains permission to modify its default branch.
- The attacker adds malicious skill instructions, configuration, or executable content to the repository.
- A user follows the documented installation command, which retrieves the current default branch without pinning or verification.
- The altered repository is written directly to
~/.codex/skills/openclaw-cli. - Codex loads or invokes the attacker-controlled skill content under the user's existing permissions.
Impact Assessment
Successful exploitation could allow attacker-controlled skill instructions or subsequently introduced code to operate with the permissions available to the user's Codex environment. Depending on the malicious content and enabled tools, the potential scope could include manipula ...[truncated 438 chars]
- Remediation
View remediation
Remediation Suggestions
- Publish reviewed releases and instruct users to check out an immutable commit hash or verified signed tag rather than the mutable default branch.
- Provide a SHA-256 checksum or cryptographic signature for each approved release and document the verification steps.
- Clone into a staging directory first, verify the revision and integrity, and only then copy the reviewed content into
~/.codex/skills/openclaw-cli. - Protect release tags and the default branch with mandatory review, branch protection, and multi-factor authentication.
- Document a secure update procedure that requires users to review changes and repeat integrity verification before replacing an installed skill.
- Prefer a versioned distribution mechanism that preserves immutable artifacts and provenance attestations.
