T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:33
- Finding
- Unpinned Global Installation of a Third-Party Extension## Vulnerability Details **File Location**: `SKILL.md`, lines 33–41 **Vulnerability Type**: Unpinned third-party dependency installed globally from mutable sources **Risk Level**: Medium ### Vulnerable Code ```markdown **From npm (recommended):** ```bash npm install -g @skysphere-labs/openclaw-bee ``` **From GitHub (latest):** ```bash npm install -g github:skysphere-labs/openclaw-bee ``` ``` ### Technical Analysis The installation instructions retrieve and globally install third-party code without pinning an audited package version or immutable Git commit. The npm command resolves the package version associated with the current distribution tag, while the GitHub command retrieves the repository's current default revision. Both sources can change after this Skill has been reviewed. The project contains only `SKILL.md`; it does not include the extension's source, a lockfile, an integrity hash, a signature, or reproducible-build information. Consequently, the effective package payload, npm lifecycle scripts, and runtime extension behavior cannot be verified from the audited artifact. Global npm installation also increases exposure because package installation scripts execute with the installing user's privileges and place executable content in a shared user or system-level npm location. This finding does not establish that the referenced package is malicious; it identifies an unsafe, mutable supply-chain trust boundary. ### Attack Path 1. An attacker compromises the npm publisher account, package distribution channel, or referenced GitHub repository. 2. The attacker publishes malicious package content or modifies the repository's default revision. 3. A user follows the documented unpinned global installation command. 4. npm retrieves the attacker-controlled version and may execute its lifecycle scripts with the installing user's privileges. 5. The user restarts the OpenClaw gateway as instructed, loading the ...[truncated 939 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the npm dependency to a specifically reviewed version instead of using the mutable latest release: ```bash npm install -g @skysphere-labs/openclaw-bee@<reviewed-version> ``` 2. If installation from GitHub is necessary, pin it to a full immutable commit SHA: ```bash npm install -g github:skysphere-labs/openclaw-bee#<full-reviewed-commit-sha> ``` 3. Publish and verify package integrity hashes or cryptographic signatures before installation. 4. Review the package contents and npm lifecycle scripts before executing the installation. 5. Prefer a project-local or otherwise isolated installation over a global installation where supported. 6. Run the extension and OpenClaw gateway under a dedicated, least-privileged operating-system account with restricted filesystem and credential access. 7. Provide a lockfile, software bill of materials, source reference, and reproducible-build instructions so the reviewed source can be matched to the installed artifact. 8. Consider initially installing with lifecycle scripts disabled for inspection, then enabling only scripts that have been explicitly reviewed.