T08 · Insecure Dependencies
Warning
- Location
- README.md:31
- Finding
- Unpinned Installation from a Mutable Git Repository## Vulnerability Details **File Location**: `README.md`, lines 31-36 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium ### Vulnerable Code ```bash # Clone to your OpenClaw workspace cd ~/openclaw-workspace/skills git clone https://github.com/QiaoTuCodes/openclaw-skill-minimax-tracker.git # Or copy manually cp -r openclaw-skill-minimax-tracker ~/openclaw-workspace/skills/ ``` ### Technical Analysis The documented installation procedure clones the default branch of a repository controlled through a personal GitHub account. It does not pin the installation to an audited commit, signed tag, or checksum-verified release. Consequently, the files installed by following these instructions may differ from the files covered by this audit. The effective payload remains mutable: the repository owner, a compromised maintainer account, or an attacker who gains repository access could replace `minimax_tracker.py` or add other executable Skill content after review. The flagged badge and release links at `README.md:12-14` do not themselves download or execute an executable. They are external links and images. The relevant supply-chain exposure is the unpinned `git clone` instruction followed by execution of repository code. ### Attack Path 1. An attacker compromises the upstream GitHub account or obtains write access to the repository. 2. The attacker modifies the default branch and inserts malicious code into `minimax_tracker.py` or another Skill file. 3. A user follows the documented `git clone` installation procedure, receiving the modified branch rather than the audited artifact. 4. The user or OpenClaw agent invokes the altered tracker through the documented `status`, `add`, or `compact` commands. 5. The injected code executes with the permissions and environment of that user or agent. ### Impact Assessment Successful exploitation could execute arbitrary code with the privileges of the user o ...[truncated 475 chars]
- Remediation
- ## Remediation Suggestions - Pin installation instructions to a specific reviewed commit hash rather than the mutable default branch. - Alternatively, distribute a versioned release archive and publish its SHA-256 checksum. - Use signed Git tags or release attestations and document signature verification before installation. - Instruct users to inspect or verify downloaded content before invoking any Skill script. - Configure the repository with protected branches, mandatory review, strong maintainer authentication, and restricted release permissions. - Prefer a trusted package or Skill distribution channel that provides immutable versions and provenance verification.