T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16–24
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
markdown openclaw: requires: tools: [filesystem] install: "npx clawhub install trades-longevity-training" --- # Trades Longevity Training `npx clawhub install trades-longevity-training`Technical Analysis
The installation instructions invoke the
clawhubnpm package throughnpxwithout specifying an exact version, integrity hash, lockfile, or trusted registry. Depending on the local npm andnpxconfiguration, the command may download and execute the package version currently selected by the package registry.Because the resolved package can change after this Skill has been reviewed, the effective installation code is not fully represented by the audited project. Compromise of the upstream package, its publishing account, or the configured package registry could therefore turn this documented installation step into a supply-chain execution vector.
The audit did not establish that the current
clawhubpackage is malicious. The issue is that the command executes mutable, externally supplied package code without a mechanism that binds installation to a specifically reviewed artifact.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or a package registry used by the victim. - The attacker publishes a malicious package version that can be selected by the unpinned
npxcommand. - A user or automation system follows the installation instruction in
SKILL.md. npxresolves and downloads the attacker-controlled package version.- Package lifecycle behavior or the invoked CLI executes with the privileges of the user running the command.
- The malicious package can access resources available to that user, subject to operating-system and sandbox restrictions.
Impact Assessment
Successful exploitation could ...[truncated 543 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to an exact, reviewed version, for example:
sh npx --yes clawhub@<reviewed-exact-version> install trades-longevity-training -
Verify the selected package artifact against a trusted integrity digest or signed provenance before execution.
-
Explicitly use the intended official package registry and prevent fallback to untrusted registries or mirrors.
-
Prefer installing dependencies from a lockfile and then invoking the locally installed binary rather than allowing transient resolution at execution time.
-
Disable or carefully review dependency lifecycle scripts where compatible with the installation process.
-
Run installation in a least-privileged, isolated environment without unnecessary credentials or access to sensitive files.
-
Document the reviewed package version and update it only through a controlled dependency-review process.
-
