T08 · Insecure Dependencies
Warning
- Location
- README.md:14
- Finding
- Unpinned Remote Package Execution in Installation Instructions## Vulnerability Details **File Location**: `README.md`, lines 14-16 **Vulnerability Type**: Execution of a mutable third-party package version **Risk Level**: Medium ```bash npx clawhub@latest install humanizer ``` ### Technical Analysis The documented installation command uses `npx` to download and execute the `latest` version of the third-party `clawhub` package. The `latest` tag is mutable, and neither a fixed package version nor an integrity value is provided. Consequently, the code executed by this command may differ from the version that existed when the project was audited. `npx` executes the downloaded package with the permissions of the user running the command. If the package, its publishing account, or an upstream dependency is compromised, malicious package or lifecycle code could run during installation. Pinning only the Skill version would not address this exposure because the installer package itself is currently unpinned. ### Attack Path 1. An attacker compromises the `clawhub` package, its registry publishing credentials, or a dependency included in a future release. 2. The attacker publishes a malicious release and assigns it to the mutable `latest` distribution tag. 3. A user follows the installation command from `README.md`. 4. `npx` retrieves and executes the attacker-controlled release. 5. The malicious code operates with the invoking user's privileges and may access resources available to that account. ### Impact Assessment Successful exploitation could permit arbitrary code execution under the invoking user's account. Depending on that account's permissions and environment, the malicious package could read or modify project and user files, access environment variables or locally stored credentials, alter installed Skill content, or download additional payloads. The command does not directly grant administrative privileges. The attainable scope is limited to the permissions and credentials avai ...[truncated 110 chars]
- Remediation
- ## Remediation Suggestions 1. Replace the mutable `latest` tag with an explicitly reviewed package version: ```bash npx clawhub@<reviewed-version> install humanizer ``` 2. Commit an appropriate lockfile where the installation workflow permits it, and ensure transitive dependencies are resolved to reviewed versions. 3. Verify package integrity and provenance using registry checksums, signatures, or attestations before execution. 4. Retrieve packages only from an explicitly configured, trusted registry rather than relying on ambient registry configuration. 5. Review package lifecycle scripts and dependencies before publishing the recommended installation command. 6. Run installation from a minimally privileged account or isolated environment without unrelated credentials or sensitive files. 7. Establish a controlled update process in which newer installer versions are reviewed and tested before the documentation is updated.