T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Executable npm Dependency Creates a Supply-Chain Risk
- Content
View full analysis
=18 - npm packages: - name: openclaw-decentralized-agent-cloud source: npm version: ">=0.1.0" verified_repo: https://github.com/openclaw/openclaw-decentralized-agent-cloud ``` The installation instructions also resolve the package without specifying an exact version: ```bash # Via npm npm install openclaw-decentralized-agent-cloud # Via ClawHub clawhub install decentralized-agent-cloud ``` ### Technical Analysis The dependency constraint `>=0.1.0` accepts every subsequent compatible or incompatible release selected by the package resolver. The direct npm command similarly installs the registry's current default release rather than a previously audited artifact. An npm package can contain executable runtime code and npm lifecycle scripts. Consequently, package installation may execute code with the permissions of the user running npm. The `verified_repo` value identifies an expected source repository but does not cryptographically bind the installed registry artifact to a reviewed commit, exact version, or integrity digest. The audited project contains only `SKILL.md`; it does not include the dependency implementation, a lockfile, or an integrity hash. The actual behavior of the package and its installation scripts therefore could not be verified from this artifact. This finding establishes an unsafe dependency-resolution practice, not evidence that the currently published package is malicious. ### Attack Path 1. An attacker compromises the npm publisher account, build pipeline, source repository, or another component involved in publishing `openclaw-decentralized-agent-cloud`. 2. The attacker publishes a new package release satisfying `>=0.1.0` or changes the release selected by the unver ...[truncated 1151 chars]- Remediation
View remediation
