T08 · Insecure Dependencies
Warning
- Location
- README.md:35
- Finding
- Unpinned Packages Executed Through npx## Vulnerability Details **File Location**: `README.md`, lines 35–41 **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: Medium **Vulnerable Code Snippet**: ```bash npx skills add cofounder-im/openclaw-cofounder-skill ``` ```bash npx clawhub install cofounder-im ``` ### Technical Analysis The installation instructions invoke the `skills` and `clawhub` npm packages through `npx` without specifying reviewed package versions or integrity hashes. If these packages are not already available locally, `npx` may retrieve their current releases from the configured npm registry and immediately execute their CLI code. Consequently, the effective executable payload can change after this Skill has been reviewed. The repository argument supplied to `skills add` identifies the Skill source, but it does not pin or verify the executable `skills` package itself. The same issue applies to the `clawhub` command. This is a supply-chain weakness rather than evidence that the currently published packages are malicious. Exploitation would require compromise of a relevant package, publisher account, registry, dependency, or package-resolution path. ### Attack Path 1. An attacker compromises a relevant npm publisher account, package release, transitive dependency, registry path, or similarly applicable package-resolution source. 2. The attacker publishes a malicious version that remains compatible with the unversioned command. 3. A user follows the documented installation instructions. 4. `npx` resolves and downloads the mutable package version from the configured registry. 5. The downloaded package's CLI or lifecycle code executes with the privileges of the user running the command. 6. The malicious code can access resources available to that user before or during Skill installation. ### Impact Assessment Successful exploitation could execute arbitrary code with the installing user's privileges. Dependin ...[truncated 579 chars]
- Remediation
- ## Remediation Suggestions 1. Pin each executable package to a reviewed exact version, for example: ```bash npx --yes skills@<reviewed-exact-version> add cofounder-im/openclaw-cofounder-skill npx --yes clawhub@<reviewed-exact-version> install cofounder-im ``` 2. Verify that the package name, publisher, registry, and expected version are explicitly documented. 3. Prefer installing dependencies through a lockfile-backed workflow with npm integrity metadata rather than resolving mutable versions at execution time. 4. Publish checksums, signatures, or provenance attestations for reviewed releases and verify them before execution. 5. Disable or review lifecycle scripts where practical, and run installation in a sandbox or minimally privileged environment without unrelated secrets. 6. Establish a controlled upgrade process in which new versions are reviewed and tested before the documentation is updated.