T08 · Insecure Dependencies
- Location
README.md:32- Finding
Mutable ClawHub Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:32andSKILL.md:42
Vulnerability Type: Unpinned third-party package execution
Risk Level: HighVulnerable Code
README.md:32:bash npx clawhub@latest install react-performanceSKILL.md:42:bash npx clawhub@latest install react-performanceTechnical Analysis
The installation instructions use
npxto download and execute theclawhubpackage. The@latesttag is mutable and does not identify a specific, audited package version or integrity hash. Consequently, the code executed by this command can change after the skill itself has been reviewed.When the package is not already available locally,
npxresolves it through the configured npm registry, downloads it, and runs its executable. Security therefore depends on the current registry package, its maintainers, the registry resolution configuration, and the package's transitive dependency chain. A compromised maintainer account, malicious future release, dependency compromise, or registry substitution could turn the documented installation command into an arbitrary-code execution channel.Attack Path
- An attacker compromises the
clawhubpackage, one of its dependencies, its publishing account, or the registry resolution path. - The attacker publishes or causes resolution of a malicious version under the mutable
latesttag. - A user follows the installation instructions and runs
npx clawhub@latest install react-performance. npxdownloads the currently resolved package rather than a previously audited immutable artifact.- Malicious package installation logic or CLI code executes with the privileges of the user running the command.
- The malicious code can access resources available to that user and may alter the local environment.
Impact Assessment
Successful exploitation permits arbitrary command execution under the installing user's acc ...[truncated 440 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Verify the selected release against its published integrity hash, provenance, signature, and source repository before recommending execution.
- Document the expected package registry and use a trusted registry configuration to reduce dependency-confusion and registry-substitution risks.
- Commit an appropriate lockfile where installation occurs through a package manager, and require integrity verification for direct and transitive dependencies.
- Avoid executing remotely resolved packages directly when possible. Install a reviewed version first and invoke its local binary.
- Consider disabling lifecycle scripts with
--ignore-scriptswhen compatible with the package, while recognizing that the CLI itself still executes code. - Use a restricted account or isolated environment for installation and do not expose production credentials or unrelated secrets to the process.
- Keep the command consistent in both
README.mdandSKILL.mdso an unsafe copy does not remain after remediation.
- Replace
