T08 · Insecure Dependencies
- Location
README.md:5- Finding
Unpinned npm Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5-7
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
markdown ## Install ```bash npx clawhub install short-video-scripttext ### Technical Analysis The installation instructions invoke `clawhub` through `npx` without specifying a reviewed package version or integrity value. If the package is not already available locally, `npx` may retrieve the currently published npm package and immediately execute it with the invoking user's permissions. Because the resolved package version is mutable and its implementation is not included in this repository, the code ultimately executed by this command cannot be verified from the audited files. Compromise of the npm package, its dependencies, its publishing account, or the relevant package-resolution path could cause attacker-controlled code to run during installation. No malicious payload was found in the audited project itself. The risk arises from the unpinned external installation dependency. ### Attack Path 1. An attacker compromises the `clawhub` npm package, one of its transitive dependencies, or an associated publishing account. 2. The attacker publishes a malicious package version that is eligible for resolution by the unversioned `npx clawhub` command. 3. A user follows the installation command documented in `README.md`. 4. `npx` retrieves and executes the attacker-controlled package version. 5. The malicious installation process runs with the permissions of the invoking user and can access resources available in that execution context. ### Impact Assessment Successful exploitation could permit arbitrary code execution with the privileges of the user running the installation command. Depending on that user's environment, the executed package could read or modify local files, access environment variables and developer credentials, alter p ...[truncated 259 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specific, reviewed version rather than relying on the latest resolvable release. - Verify the package's official npm identity, provenance, maintainers, and release integrity before recommending execution.
- Use lockfiles and integrity metadata where the installation workflow supports them.
- Prefer a workflow that separates package download and inspection from execution.
- Document the expected official package registry and source repository to reduce dependency-confusion and package-spoofing risk.
- Periodically review the pinned release and its transitive dependencies before updating it.
- Pin
