T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned ClawHub Package Is Downloaded and Executed Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:17andREADME.md:30
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
bash npx clawhub@latest install design-system-creationTechnical Analysis
The documented installation command instructs
npxto retrieve and execute the mutablelatestrelease of the third-partyclawhubpackage. The package version and integrity are not pinned to an artifact reviewed as part of this audit.The behavior of the installation process can therefore change without any modification to this repository. If the npm package, publisher account, release pipeline, or package registry is compromised, a malicious release could be selected by the
latesttag. Running the command would execute the retrieved package's CLI code and potentially its npm lifecycle scripts.Attack Path
- An attacker compromises the
clawhubnpm publisher account, package pipeline, or another component of its distribution chain. - The attacker publishes a malicious package version and assigns it to the
latestdistribution tag. - A user follows the installation instructions in
SKILL.mdorREADME.md. npxdownloads the attacker-controlled version.- The malicious package executes with the privileges of the user running the installation command.
- The package can alter project files, access user-readable information, install modified Skill instructions, or perform other actions available to that user.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. The accessible scope may include the current project, user-owned configuration and credential files, environment variables, and other resources available to that account. The command does not directly request elevated privileges, so system-wide impact depends on the user's existing permissions and execution env ...[truncated 9 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an exact, reviewed package version. - Verify the package's publisher, repository, and release provenance before recommending it.
- Use npm lockfiles and integrity metadata where the installation workflow supports them.
- Prefer a workflow that downloads a fixed artifact for inspection before executing it.
- Document the expected package checksum or signature and require verification.
- Run installation in a restricted environment with only the filesystem and network permissions necessary for the task.
- Periodically review pinned dependency versions and update them only after security validation.
- Replace
