T08 · Insecure Dependencies
- Location
README.md:19- Finding
Unpinned Third-Party Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 19–21
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
bash npx clawhub@latest install the-molt-readerTechnical Analysis
The documented installation command uses
npxto download and execute the mutablelatestrelease of the third-partyclawhubpackage. No exact package version or integrity hash is specified.Consequently, the code executed by this command may differ from the version that was available when the Skill was audited. If the package, its publisher account, its dependency chain, or the package registry is compromised, the installation command could execute attacker-controlled code. A future legitimate but insecure release could create the same exposure.
This finding concerns the optional installation route documented in the README. The audited Skill itself contains only text files and does not ship executable code.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, a transitive dependency, or the package-distribution channel. - The attacker publishes a malicious release that becomes the version resolved by the
latesttag. - A user follows the documented command and invokes
npx clawhub@latest. npxretrieves and executes the newly resolved package.- Malicious package lifecycle or runtime code executes with the privileges and environmental access of the user running the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. Depending on that account's privileges and environment, the malicious package could access user-readable files, credentials exposed to the process, project data, and network resources, or modify local state.
The impact is limited by the privileges of the invoking user and any operating-system, container, or sandbox restrictions. The audited files provide no evid ...[truncated 58 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for exampleclawhub@x.y.z. - Verify the selected package artifact using registry integrity metadata, a cryptographic checksum, or a trusted lockfile where supported.
- Prefer the platform's trusted native installation mechanism when it does not require dynamically downloading and executing an unreviewed package.
- Review new installer versions before updating the documented version.
- Use automated dependency and provenance verification, such as signed releases or package-registry provenance attestations.
- Advise users to perform installation in a least-privileged, isolated environment and not under an administrator or root account.
- Replace
