T08 · Insecure Dependencies
Warning
- Location
- README.md:93
- Finding
- Unpinned executable dependency and mutable remote installation sources<![CDATA[ ## Vulnerability Details **File Location**: `README.md`, lines 93-120 **Vulnerability Type**: Unpinned executable dependency and mutable supply-chain source **Risk Level**: Medium ### Vulnerable Code ```bash git clone https://github.com/hundevmode/boosta-long-to-shorts-openclaw-skill.git cd boosta-long-to-shorts ``` ```bash npx skills add hundevmode/boosta-long-to-shorts-openclaw-skill --skill boosta-long-to-shorts ``` ```bash npx skills add https://github.com/hundevmode/boosta-long-to-shorts-openclaw-skill --list ``` ### Technical Analysis The installation instructions invoke `npx skills` without an exact package version and retrieve the Skill from a GitHub repository without pinning a commit hash or signed release. Both sources are mutable, so the code executed or installed in the future may differ from the audited artifact. `npx` can download and execute the currently resolved npm package. If that package, its dependencies, or its publishing account is compromised, malicious code could run during installation. Similarly, cloning or installing from the repository’s default branch trusts all subsequent upstream changes. No malicious dependency or compromised upstream source was identified in the audited files. The vulnerability is the absence of version pinning and integrity verification. ### Attack Path 1. An attacker compromises the npm package, one of its dependencies, the package publisher, or the referenced GitHub repository. 2. The attacker publishes a malicious package version or modifies the repository’s default branch. 3. A user follows the README and runs the unversioned `npx skills` command or clones the mutable branch. 4. The compromised CLI or repository content executes or installs with the invoking user’s privileges. 5. The malicious component can access resources available to that user and may install a Skill that influences later agent operations. ### Impact Assessment Successful exploitation could provide code execution ...[truncated 718 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin the executable npm package to a reviewed exact version, for example: ```bash npx skills@X.Y.Z add ... ``` 2. Pin GitHub installation references to an audited commit hash or immutable signed release tag rather than the default branch. 3. Publish cryptographic checksums or signatures for release artifacts and document how users should verify them before installation. 4. Use npm lockfiles and integrity metadata wherever package installation is part of the supported workflow. 5. Recommend reviewing downloaded content before execution, particularly before granting access to credentials such as `BOOSTA_API_KEY`. 6. Protect upstream publisher and repository accounts with multi-factor authentication, restricted release permissions, branch protection, and signed commits or releases. ]]>