T08 · Insecure Dependencies
- Location
README.md:8- Finding
Unpinned Third-Party Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:8
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code:
bash npx clawhub@latest install bmi-trackerTechnical Analysis
The documented installation command instructs
npxto retrieve and execute the mutablelatestrelease of the third-partyclawhubnpm package. The dependency is not pinned to a reviewed version, and the command does not enforce an integrity hash or another verification mechanism.Because
npxcan download and immediately execute package code, the effective installer may change after this skill has been reviewed. The installer source is not included in the audited artifact, so its behavior cannot be validated from the project files. Exploitation depends on compromise or malicious replacement of the upstream package, its publishing account, or the package distribution channel.Attack Path
- An attacker compromises the
clawhubnpm package, a maintainer account, or its distribution channel. - The attacker publishes a malicious release that becomes the package's
latestversion. - A user follows the installation command in
README.md. npxdownloads and executes the attacker-controlled package.- The malicious package runs with the privileges and environmental access of the user who invoked the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. The resulting scope may include reading or modifying files accessible to that user, accessing environment variables and credentials available to the process, making network requests, and installing additional user-level components. Elevated system-wide impact would require the command to be run from an already privileged account or combined with a separate privilege-escalation vulnerability.
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version. - Publish and verify the expected package integrity digest before execution.
- Use a trusted, explicitly configured package registry.
- Review the selected installer version and document its expected behavior and required permissions.
- Prefer a lockfile-backed installation workflow where applicable.
- Avoid automatically executing newly downloaded package code when a non-executing installation or locally reviewed installer is available.
- Establish a controlled update process in which newer versions are reviewed and integrity-pinned before the documentation is updated.
- Replace
