T08 · Insecure Dependencies
- Location
README.md:18- Finding
Unpinned npm Package Execution in English Installation Guide
- Content
View full analysis
Vulnerability Details
File Location:
README.md:18
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable code:
bash npx clawhub install maxhub-weiboTechnical Analysis
The installation guide instructs users to execute
clawhubthroughnpxwithout specifying an exact, audited package version or verifying package integrity. If the package is not already available locally,npxmay retrieve its current release from the configured npm registry and execute it immediately.Consequently, the code executed by this command can change after the Skill has been reviewed. Compromise of the npm package, its publisher account, the registry resolution path, or a future package release could result in unreviewed code running under the installing user's account.
Attack Path
- An attacker compromises the npm package, its publisher credentials, or another component of the package-resolution chain.
- The attacker publishes a malicious or backdoored release that resolves under the unversioned
clawhubpackage name. - A user follows the installation command in
README.md. npxdownloads the currently resolved package because no exact version is pinned.- The package executes with the privileges of the user running the command.
- The malicious package can access resources available to that user and may install additional components.
Impact Assessment
Successful exploitation would provide code execution with the installing user's privileges. Depending on the execution environment, the malicious package could read user-accessible files and environment variables, including API credentials; modify project or user configuration; make arbitrary network requests; or install persistence where the user has sufficient permissions. The command does not inherently grant administrative privileges, so the maximum scope is bounded by the privileges of the invoking acc ...[truncated 5 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to an exact version that has been reviewed, for example:
bash npx --yes clawhub@AUDITED_EXACT_VERSION install maxhub-weibo - Do not use a floating tag such as
latestor a semver range. - Document the expected npm package publisher, registry, version, and package digest.
- Prefer a trusted, separately installed CLI whose provenance and integrity have already been verified.
- Where supported, verify package signatures or registry integrity metadata before execution.
- Re-audit the pinned package before updating the documented version.
- Pin the CLI to an exact version that has been reviewed, for example:
