T08 · Insecure Dependencies
- Location
README.md:15- Finding
Unpinned Third-Party Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Locations:
README.md:15,README_CN.md:15
Vulnerability Type: Unpinned package execution throughnpx
Risk Level: MediumComplete Code Snippet:
bash npx clawhub install admapixTechnical Analysis
The documented installation command invokes the
clawhubpackage throughnpxwithout specifying a reviewed version or integrity constraint. Depending on the local npm configuration and cache state,npxcan retrieve the current package release from the configured registry and execute its command-line entry point.The effective installer implementation is not included in this project, so it was outside the reviewed artifact and may change after this Skill version has been audited. This creates a supply-chain trust boundary in which an upstream package compromise, registry-account takeover, malicious replacement, or unexpectedly unsafe future release could introduce executable behavior.
The audit did not establish that the current
clawhubpackage is malicious. The confirmed issue is that the installation instructions do not constrain users to a specific reviewed release.Attack Path
- An attacker compromises the package publisher, registry account, distribution channel, or a future upstream
clawhubrelease. - The attacker publishes a modified package version containing malicious lifecycle or command-line code.
- A user follows the documented
npx clawhub install admapixcommand. npxresolves and downloads the attacker-controlled or compromised package version.- The package executes with the privileges and environment of the user running the installation command.
- The malicious package can access resources available to that process, including user files, environment variables, network access, and writable configuration locations.
Impact Assessment
Successful exploitation could obtain the same effective privileges as the user running `n ...[truncated 674 chars]
- An attacker compromises the package publisher, registry account, distribution channel, or a future upstream
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specific version that has been reviewed, rather than allowing unconstrained resolution of the latest release. - Publish the expected package version and registry source explicitly in both installation guides.
- Where supported, verify the downloaded package against a documented integrity hash or signed provenance record.
- Use a lockfile or equivalent immutable dependency mechanism for automated installation and CI environments.
- Configure trusted registry scopes and prevent fallback to untrusted or unexpected package registries.
- Review new
clawhubversions before updating the pinned version, including command entry points and lifecycle scripts. - Run installation under a non-privileged account with minimal filesystem access and without unrelated secrets in the environment.
- Apply the same corrected command to both
README.mdandREADME_CN.mdso localized documentation does not retain the unsafe installation path.
- Pin
