T08 · Insecure Dependencies
- Location
README.md:5- Finding
Unpinned npm CLI Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:5-8
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code:
markdown ## Install ```bash npx clawhub install mediaclawtext ### Technical Analysis The documented installation command invokes `clawhub` through `npx` without specifying an exact package version or integrity value. If the package is not already available locally, `npx` can retrieve and execute the package distributed under that mutable npm registry name. Because the dependency is not pinned, the code executed when users follow these instructions may differ from the version that was available when this project was audited. This creates a supply-chain trust boundary in which compromise of the package, its publisher account, or its transitive dependencies could result in attacker-controlled code being executed during installation. ### Attack Path 1. An attacker compromises the npm publisher account, package, release process, or a relevant transitive dependency for `clawhub`. 2. The attacker publishes a malicious version under the same package name. 3. A user follows the installation command from `README.md`. 4. `npx` resolves and downloads the current mutable package version. 5. The malicious CLI or applicable package lifecycle code executes with the privileges of the user running the command. 6. The payload can access resources available to that user and may alter the installation process or install a modified Skill. ### Impact Assessment Successful exploitation could permit arbitrary code execution under the installing user's account. The accessible scope could include user-readable files, environment variables, credentials available to the process, writable project files, and network resources reachable by that user. If the command is run from a privileged account or environment, the impact would increase accordingly. Exploitation depends ...[truncated 149 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto an exact, reviewed version instead of resolving the latest available release, for example by using an exact version in thenpxcommand. - Verify and document the package's official registry namespace and publisher identity.
- Use npm lockfiles and registry integrity metadata where installation architecture permits.
- Review the pinned package and its transitive dependency tree before recommending execution.
- In automated or sensitive environments, download and verify the package artifact before execution rather than allowing transient retrieval and immediate execution.
- Add a controlled upgrade process that reviews new package versions before changing the documented version.
- Advise users not to run the installation command with elevated privileges.
- Pin
