T08 · Insecure Dependencies
- Location
README.md:13- Finding
Execution of an Unpinned Third-Party Package During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 13-17
Vulnerability Type: Supply-chain exposure through a mutable package version
Risk Level: MediumVulnerable Code Snippet:
markdown ## Installation ```bash npx clawhub@latest install social-media-managertext ### Technical Analysis The documented installation command uses `npx` to retrieve and execute the `clawhub` npm package identified by the mutable `@latest` tag. Because neither an exact package version nor an integrity hash is specified, the code executed by this command can change after the Skill has been reviewed. This artifact does not contain evidence that the referenced package is currently malicious. However, the installation mechanism creates a supply-chain trust boundary: compromise of the package, its maintainer account, or the configured npm registry could cause users to execute attacker-controlled code. Package lifecycle hooks or the CLI entry point may run with the permissions of the user invoking `npx`. ### Attack Path 1. An attacker compromises the `clawhub` npm package, its publisher credentials, or the registry path from which it is resolved. 2. The attacker publishes a modified release and causes it to become the version referenced by `@latest`. 3. A user follows the installation instructions and runs: `npx clawhub@latest install social-media-manager`. 4. `npx` downloads the mutable package release and executes its CLI or applicable lifecycle behavior. 5. The attacker-controlled code runs locally with the invoking user's privileges. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the account running the installation command. Depending on that account's privileges and environment, the malicious package could access user-readable files, environment variables, authentication material, project data, or network resources, and could modify files writable by that us ...[truncated 270 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Verify the package against an expected integrity digest before execution.
- Document the trusted npm registry and package publisher so package resolution cannot silently use an unintended source.
- Use a lockfile or another reproducible installation mechanism where supported.
- Review package lifecycle scripts and CLI entry points before recommending execution.
- Run installation with a non-privileged account and avoid
sudoor administrator execution. - Consider separating package download from execution so users can inspect and verify the resolved artifact first.
- Replace
