T08 · Insecure Dependencies
- Location
README.md:6- Finding
Unpinned Package Runner Executes the Latest Published Installer
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5–7
Vulnerability Type: Unpinned third-party package execution
Risk Level: Mediumbash npx clawhub@latest install budget-plannerTechnical Analysis
The documented installation command instructs users to execute the mutable
latestrelease of the third-partyclawhubnpm package. Because thelatestdistribution tag can be reassigned after this skill has been reviewed, the command does not guarantee that users execute the same installer version that was originally assessed.npxmay download the selected package and execute its command-line entry point. If the package, publisher account, release process, or npm distribution tag is compromised, an attacker could publish a malicious release and pointlatestto it. Following the documented installation instructions would then execute attacker-controlled package code.No evidence in the audited files establishes that the current
clawhubpackage is malicious. The issue is the unsafe, mutable dependency reference and the resulting supply-chain exposure.Attack Path
- An attacker compromises the upstream package publisher, publishing pipeline, or npm account associated with
clawhub. - The attacker publishes a malicious package release and assigns the
latestdistribution tag to that release. - A user follows the README and runs
npx clawhub@latest install budget-planner. npxretrieves the attacker-controlled release and invokes its executable.- The malicious package executes with the permissions and environmental access of the invoking user.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the account running the installation command. Depending on that account's privileges and environment, exposed resources could include user files, project credentials, environment variables, authentication tokens, and writable application config ...[truncated 246 chars]
- An attacker compromises the upstream package publisher, publishing pipeline, or npm account associated with
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith a specifically reviewed, immutable version, for example:bash npx clawhub@X.Y.Z install budget-planner - Establish a process for reviewing and deliberately updating the pinned version rather than accepting automatic distribution-tag changes.
- Where supported, verify package provenance, signatures, and registry integrity metadata before execution.
- Use a trusted registry and enforce lockfile or package-manager integrity controls when integrating the installer into an automated workflow.
- Run installation with the minimum required privileges and avoid exposing unrelated secrets in the process environment.
- For higher-assurance environments, download and inspect the package artifact before running it rather than combining retrieval and execution in one command.
- Replace