T08 · Insecure Dependencies
Warning
- Location
- README.md:178
- Finding
- Unpinned Third-Party Package Execution via npx## Vulnerability Details **File Location**: `README.md:178` **Vulnerability Type**: Insecure dependency installation using a mutable package tag **Risk Level**: Medium ### Vulnerable Code ```bash npx clawhub@latest install feedoracle-compliance ``` ### Technical Analysis The documented installation command instructs `npx` to retrieve and execute the `latest` release of the third-party `clawhub` package. The `latest` tag is mutable, so the code executed by this command can change after this Skill has been reviewed. The project does not include a package lockfile, integrity hash, signature-verification procedure, or local copy of that package through which the executed version can be independently audited. This is a supply-chain weakness rather than evidence that the current package is malicious. Exploitation would require compromise of the package, its publisher account, or its distribution channel, or publication of an unexpectedly unsafe release under the mutable tag. ### Attack Path 1. An attacker compromises the package publisher account, package registry, or release process associated with `clawhub`. 2. The attacker publishes a malicious release and assigns it to the mutable `latest` tag. 3. A user follows the installation instructions and runs the documented `npx` command. 4. `npx` downloads and executes the attacker-controlled package code. 5. The malicious package operates with the permissions of the user who launched the command and can access resources available to that account. ### Impact Assessment Successful exploitation could result in arbitrary code execution under the installing user's privileges. Depending on the user's environment and permissions, the malicious package could read or alter user-accessible files, access environment variables and credentials available to the process, modify local configuration, make network requests, or install additional components. The scope is normally limited to the ...[truncated 125 chars]
- Remediation
- ## Remediation Suggestions - Replace the mutable `@latest` tag with an exact, reviewed package version. - Publish the expected package version and integrity digest alongside the installation instructions. - Where supported, require registry provenance or publisher-signature verification before installation. - Document how users can inspect the package and verify its checksum before execution. - Recommend running installation without elevated privileges and within a restricted or disposable environment. - Establish a controlled update process in which new versions are reviewed before the pinned version is changed.