T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Package Execution in Installation Command
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 13
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code Snippet:
yaml install: "npx clawhub install howtousehumans/basic-home-repair"Technical Analysis
The installation command invokes
clawhubthroughnpxwithout specifying an exact package version or an integrity constraint. If the package is not already available in the local environment,npxcan retrieve package code dynamically from the configured package registry and execute it with the privileges of the installing user.Because the resolved package can change after this Skill has been audited, the effective installation code is not immutable. Compromise of the package publisher, registry account, distribution channel, or a subsequently published package version could cause the command to execute code that was not present during this review.
This is a supply-chain weakness rather than evidence that the currently referenced package is malicious.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or its package distribution channel. - The attacker publishes a modified release containing malicious installation or runtime behavior.
- A user follows the Skill metadata and runs the unpinned
npx clawhub install howtousehumans/basic-home-repaircommand. npxresolves and downloads the package version currently provided by the configured registry.- The downloaded package code executes with the installing user's privileges.
- The malicious code can access resources available to that user, subject to operating-system and environment restrictions.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the account running the installation command. Potential scope includes reading or modifying user-accessible files, accessing environment variables and credenti ...[truncated 413 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto an exact, reviewed version rather than allowing dynamic resolution, for example:yaml install: "npx --yes clawhub@<audited-exact-version> install howtousehumans/basic-home-repair" - Pin the installed Skill or package to an immutable version, digest, or commit if the installer supports that capability.
- Verify package provenance through registry signatures, checksums, integrity hashes, or an approved internal package mirror.
- Record the expected registry and package publisher so a modified registry configuration cannot silently redirect dependency resolution.
- Review the resolved dependency tree and retain a lockfile or equivalent integrity manifest where supported.
- Run installation with a non-privileged account in a sandbox or restricted environment, and do not invoke it with administrative privileges.
- Consider installing a previously verified CLI artifact separately and changing the metadata to invoke that trusted local executable instead of downloading and executing package code on demand.
- Pin
