T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27-30
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumComplete Code Snippet:
markdown Here is an example of how to use this skill: ```bash npx clawhub install test-skill-from-tpclawhubtext ### Technical Analysis The documented command invokes `clawhub` through `npx` without specifying a package version or integrity constraint. If the package is not already available locally, `npx` may retrieve the current package release from the configured npm registry and execute its code with the invoking user's privileges. Because the effective package contents can change after this skill has been reviewed, users cannot determine from the repository alone what code will execute. The project contains no lockfile, package manifest, integrity hash, verified local implementation, or trusted version constraint for the referenced CLI. This is a supply-chain weakness rather than evidence that the current `clawhub` package is malicious. ### Attack Path 1. An attacker compromises the npm account, package publication process, registry resolution path, or a future release of the referenced `clawhub` package. 2. The attacker publishes a modified package version containing malicious installation or runtime behavior. 3. A user follows the documented `npx clawhub install test-skill-from-tpclawhub` command. 4. `npx` resolves and downloads the attacker-controlled package version when no trusted local version is available. 5. The malicious package executes under the user's account and inherits the command's environment and accessible resources. ### Impact Assessment Successful exploitation could provide code execution with the privileges of the user running the command. Depending on that user's permissions and environment, the package could access readable files, environment variables, developer credentials, source repositorie ...[truncated 439 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a reviewed, trusted version rather than allowing implicit resolution of the latest release, for example:
bash npx --yes clawhub@<reviewed-version> install test-skill-from-tpclawhub - Document the package's official publisher, registry, and source repository so users can verify package provenance.
- Prefer installing the CLI as a declared project dependency with a committed lockfile and then invoking the locked local binary.
- Where supported, verify registry integrity metadata, package signatures, provenance attestations, or published checksums before execution.
- Run package-management commands with least privilege and without unnecessary secrets in the environment.
- Add explicit dependency and installation documentation; the current references to “required dependencies” and a “main script” do not identify any corresponding project files.
- Pin the CLI to a reviewed, trusted version rather than allowing implicit resolution of the latest release, for example:
