T08 · Insecure Dependencies
- Location
SKILL.md:37- Finding
Unpinned Installer Package Executed Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:37
Vulnerability Type: Unpinned third-party installer execution
Risk Level: MediumVulnerable Code
bash npx clawdhub@latest install predicate-snapshotTechnical Analysis
The documented installation procedure instructs users to download and execute the package currently associated with the mutable npm
latesttag. Neither an exact package version nor an independently verifiable integrity value is specified.Consequently, the installer executed by a future user may differ from the installer reviewed when this Skill was audited. Compromise of the package publisher, npm account, release pipeline, or package namespace could turn the installation command into an arbitrary-code execution channel. The package name should also be explicitly verified against the intended official publisher because it differs from the “ClawHub” branding used elsewhere in the documentation.
This is a supply-chain weakness rather than evidence that the current package is malicious.
Attack Path
- An attacker compromises the referenced npm package, its publisher account, or its release pipeline.
- The attacker publishes a malicious package release and assigns it the
latestdistribution tag. - A user follows the installation command in
SKILL.md. npxretrieves and executes the attacker-controlled release without requiring review of the changed payload.- The malicious installer executes with the installing user's permissions and can modify the Skill installation or other user-accessible resources.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running the installation command. The attacker could read or modify files available to that user, access environment variables and credentials exposed to the installation process, alter the OpenClaw Skill directory, or install modified Agent func ...[truncated 282 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace
@latestwith an exact, reviewed package version, for example:bash npx --yes clawdhub@X.Y.Z install predicate-snapshot -
Verify and document the package's official npm scope, exact name, publisher identity, and repository before recommending it.
-
Publish the expected package integrity hash or signed-release verification instructions.
-
Prefer downloading the installer without executing it, verifying its integrity and provenance, and only then running it.
-
Use lockfiles and immutable versions for automated installation or deployment.
-
Document the files and directories that the installer is expected to modify so users can detect behavior outside its required scope.
-
