T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Execution of an Unpinned, Mutable Package Release
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 31
Vulnerability Type: Supply-chain risk caused by unpinned package execution
Risk Level: MediumVulnerable Code:
bash npx clawhub@latest install mit-reasoning-liteTechnical Analysis
The documented installation command instructs users to execute the mutable
latestrelease of the third-partyclawhubpackage throughnpx. Depending on the local npm configuration and cache,npxcan retrieve the package from a remote registry and execute its CLI code with the invoking user's privileges.Because
latestis a mutable distribution tag rather than an immutable version, the code executed in the future may differ from the version originally reviewed. The command also provides no package-integrity value or other verification mechanism. The remotely retrieved package is not included in this project, so its implementation and lifecycle behavior cannot be validated from the audited artifact.This is an insecure dependency execution pattern, not evidence that the current
clawhubpackage is malicious.Attack Path
- An attacker compromises the package publisher account, registry delivery path, or another component involved in publishing the
clawhubpackage. - The attacker publishes a malicious package release and assigns it to the
latestdistribution tag. - A user follows the installation command in
SKILL.md. npxdownloads or resolves the attacker-controlled release.- The package's CLI or applicable package execution logic runs with the user's permissions.
- The malicious release can access or modify resources available to that user.
Impact Assessment
Successful exploitation could allow arbitrary code execution under the account that invokes
npx. The reachable scope may include user-owned files, source repositories, environment variables, locally accessible credentials, network resources, and writable configur ...[truncated 288 chars]- An attacker compromises the package publisher account, registry delivery path, or another component involved in publishing the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, reviewed package version:bash npx clawhub@X.Y.Z install mit-reasoning-lite - Verify the selected release's provenance and integrity before recommending it.
- Use npm lockfiles and integrity metadata where the installation workflow permits.
- Document the expected trusted registry and avoid allowing silent resolution from arbitrary registry mirrors.
- Prefer a locally reviewed installation path when feasible.
- Correct the local installer's references to absent
USAGE.mdandREADME.mdfiles before presenting it as an alternative, becauseset -ecurrently causes that installer to terminate partway through execution.
- Replace the mutable
