T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 14
Vulnerability Type: Unpinned third-party installer dependency
Risk Level: MediumVulnerable Code:
yaml install: "npx clawhub install howtousehumans/adult-social-skills"Technical Analysis
The installation command invokes
clawhubthroughnpxwithout specifying an audited package version or integrity hash. If the package is not already available locally,npxcan retrieve the currently resolved version from the configured npm registry and execute it with the installing user's privileges.Consequently, the code executed during installation can differ from the code that existed when this Skill was reviewed. This creates a supply-chain trust boundary in which compromise of the package publisher, registry account, package resolution process, or an upstream dependency could introduce arbitrary behavior.
Attack Path
- An attacker compromises the publisher account, package distribution channel, or another component involved in resolving the unpinned
clawhubpackage. - The attacker publishes a malicious or modified version that remains compatible with the unversioned command.
- A user runs the documented
npx clawhub install howtousehumans/adult-social-skillscommand. npxresolves, downloads, and executes the attacker-controlled package.- The malicious installer performs actions with the privileges and environmental access of the user running the command.
Impact Assessment
Successful exploitation could result in arbitrary code execution under the installing user's account. Depending on that account's privileges and environment, the payload could access local files, environment variables, credentials, project data, and network resources. If installation is performed by a privileged user or in a CI/CD environment, the impact could extend to system-wide modification, deployment credentials, build artifacts, and other con ...[truncated 22 chars]
- An attacker compromises the publisher account, package distribution channel, or another component involved in resolving the unpinned
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specific, reviewed version rather than allowingnpxto resolve the latest available release. - Use a lockfile or another reproducible dependency-resolution mechanism.
- Verify package provenance and integrity through registry signatures or cryptographic hashes where supported.
- Run installation with the least-privileged account necessary and avoid exposing unrelated credentials or sensitive environment variables.
- Review the pinned package and its transitive dependencies before updating the approved version.
- In automated environments, install dependencies from an approved internal registry or immutable artifact repository.
- Pin
