T08 · Insecure Dependencies
- Location
SKILL.md:29- Finding
Mutable Package Version Executed Through npx Installation Command
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 29
Vulnerability Type: Unpinned executable dependency
Risk Level: Mediumbash npx clawhub@latest install daily-hot-aggregatorTechnical Analysis
The documented installation command directs
npxto retrieve and execute the mutablelatestrelease of theclawhubpackage. Because no exact version or integrity value is specified, the code executed during installation can change after this Skill has been audited.This creates a supply-chain trust boundary in which control of the package registry account, publication pipeline, or package distribution infrastructure can alter the installer subsequently executed by users. The repository itself does not contain the retrieved package, so its behavior cannot be verified as part of this static audit.
Attack Path
- An attacker compromises the package maintainer account, publication credentials, build pipeline, or upstream distribution channel.
- The attacker publishes a malicious package release and causes it to resolve through the
latesttag. - A user follows the installation instructions and runs
npx clawhub@latest install daily-hot-aggregator. npxdownloads and executes the attacker-controlled package.- The malicious installer executes with the privileges and environmental access of the user who invoked the command.
Impact Assessment
Successful exploitation could allow arbitrary code execution under the installing user's account. The accessible scope may include that user's files, environment variables, credentials available to the process, network access, and writable project or configuration directories. This finding does not demonstrate that the current upstream package is malicious; it identifies the risk caused by executing a mutable, externally controlled package version.
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version. - Commit and enforce an appropriate lockfile where package-manager installation is part of the project workflow.
- Verify package provenance and integrity before execution, using registry integrity metadata, signed releases, or an equivalent trusted verification mechanism.
- Document the expected package publisher and version so users can detect substitutions.
- Review new installer versions before updating the pinned version.
- For higher-assurance environments, download and inspect the installer separately instead of allowing
npxto retrieve and execute it in one step.
- Replace
