T08 · Insecure Dependencies
- Location
README.md:5- Finding
Mutable npm Package Version Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5-7
Vulnerability Type: Unpinned third-party installation dependency
Risk Level: Mediumbash npx clawhub@latest install contact-managerTechnical Analysis
The documented installation command instructs
npxto retrieve and execute the package version referenced by the mutablelatestnpm distribution tag. Because neither an immutable version nor an integrity value is specified, the code executed by this command may change after the Skill has been audited.This creates a supply-chain risk: compromise of the package publisher, npm account, release pipeline, or a future release assigned to
latestcould cause users to execute code that was not included in the reviewed project. The repository itself contains no executable implementation that can establish or constrain the behavior of the downloaded installer.Attack Path
- An attacker compromises the
clawhubnpm publisher account, release pipeline, or another mechanism controlling thelatestpackage release. - The attacker publishes a modified package and assigns it to the
latestdistribution tag. - A user follows the installation command in
README.md. npxdownloads and executes the attacker-controlled package version.- The package runs with the operating-system privileges of the user invoking the command and may access resources available to that user.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on those privileges and the host environment, the downloaded package could access user-readable files, environment variables, credentials available to the process, network resources, or project data. System-wide impact would require the installation command to be run by a privileged user or an additional privilege-escalation mechanism.
No evidence in the reviewed files establishes that th ...[truncated 135 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an explicitly reviewed, immutable package version, such asclawhub@x.y.z. - Publish and verify package integrity information or cryptographic signatures where supported.
- Document the expected npm registry, package publisher, and package provenance so users can validate the source.
- Use lockfiles or equivalent dependency controls in automated installation workflows.
- Establish a process for reviewing each new installer version before updating the documented command.
- Advise users not to run the installer with elevated privileges unless those privileges are strictly required.
- Remove the unexplained
curlbinary requirement from_meta.json, or document and constrain its legitimate purpose, to minimize unnecessary tooling and ambiguity.
- Replace
