T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:12
- Finding
- Unpinned Third-Party Package Execution Through npx## Vulnerability Details **File Location**: `SKILL.md`, lines 12-14 **Vulnerability Type**: Unpinned executable dependency **Risk Level**: Medium ```bash npx clawhub@latest install ai-agent-setup ``` ### Technical Analysis The installation instructions invoke `clawhub` through `npx` using the mutable `latest` tag. If the package is not already available locally, `npx` may download and execute the version currently published under that tag. The project does not specify an audited version, integrity hash, lockfile, or trusted package provenance. Because `latest` can point to different package contents after this skill has been reviewed, the command creates a supply-chain risk. Compromise of the package publisher, registry account, release process, or package distribution channel could cause users to execute altered code without any corresponding change to this repository. ### Attack Path 1. An attacker compromises the `clawhub` package publisher, release pipeline, registry account, or another relevant distribution component. 2. The attacker publishes a malicious release and assigns it to the `latest` tag. 3. A user follows the documented installation command. 4. `npx` retrieves and executes the attacker-controlled package version. 5. The malicious package executes with the permissions of the user running the command and may modify files, access user-readable information, invoke network services, or install additional components. ### Impact Assessment Successful exploitation can provide arbitrary code execution under the invoking user's account. The accessible scope includes files, credentials, environment variables, network resources, and applications available to that account. If the command is run from a privileged administrative or CI/CD context, the impact may expand to system-wide resources, deployment credentials, build artifacts, or connected infrastructure. The reviewed file does not itself demonstrate privilege es ...[truncated 66 chars]
- Remediation
- ## Remediation Suggestions - Replace the mutable `latest` tag with an exact, reviewed package version, for example `npx clawhub@X.Y.Z`. - Verify that the package comes from the intended registry and publisher before execution. - Use registry-supported integrity verification or a documented cryptographic checksum where available. - Review the pinned package, including lifecycle scripts and transitive dependencies, before recommending it. - Execute installation with a non-privileged account in an isolated environment. - In automated environments, enforce dependency allowlists, lockfiles, and reproducible installation controls. - Establish a controlled process for reviewing and explicitly approving upgrades rather than tracking `latest` automatically.