T08 · Insecure Dependencies
- Location
README.md:19- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:19
Vulnerability Type: Unpinned executable dependency
Risk Level: MediumComplete Code Snippet:
bash npx clawhub@latest install miraflowTechnical Analysis
The documented installation command instructs users to download and execute the mutable
latestversion of theclawhubnpm package. No exact version, package integrity hash, or signature is specified.Because the
latesttag can be reassigned after this Skill has been audited, the code executed during installation may differ from the version expected by the project author. Exploitation requires compromise or malicious modification of the package, its publishing account, or the relevant registry metadata; no such compromise was observed in the audited files.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or relevant package-registry metadata. - The attacker publishes a malicious release and assigns it the
latesttag. - A user follows the README and runs
npx clawhub@latest install miraflow. npxretrieves and executes the attacker-controlled package.- The malicious package executes with the permissions of the user running the command.
Impact Assessment
A compromised package could access files, environment variables, credentials, and network resources available to the installing user. It could also alter the OpenClaw workspace or install modified Skill content. The command does not itself request elevated operating-system privileges, so its direct scope is limited to the invoking user's permissions.
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, audited package version. - Publish and document the expected package integrity hash or signed release provenance.
- Encourage users to inspect the resolved package version before execution.
- Use lockfiles and registry integrity verification where installation tooling supports them.
- Establish a controlled upgrade process in which new package versions are reviewed before the documented version is changed.
- Replace
