T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned npm Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:16
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: MediumVulnerable Code
yaml install: "npx clawhub install howtousehumans/emotional-regulation"Technical Analysis
The installation metadata invokes
clawhubthroughnpxwithout specifying an exact package version or integrity hash. If the package is unavailable locally,npxcan retrieve executable package content from the configured npm registry and run its CLI code with the installing user's privileges.Because dependency resolution is not pinned to a reviewed artifact, the code executed during installation can change independently of this skill's reviewed
SKILL.mdfile. A compromised maintainer account, malicious package release, registry compromise, or unexpected upstream update could therefore introduce arbitrary behavior after the audit.The repository contains only
SKILL.md; it does not include the executable installer implementation, a lockfile, or integrity metadata that would permit verification of the remotely resolved package.Attack Path
- A user or automated agent follows the installation instruction in
SKILL.md. npxresolvesclawhubfrom the configured npm registry because no exact version is specified.- An attacker publishes or causes resolution of a compromised
clawhubrelease, such as through an upstream account or supply-chain compromise. npxdownloads and executes the compromised package's CLI or lifecycle behavior.- The malicious package performs arbitrary actions within the permissions and accessible environment of the installing process.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user or service account running the installation command. Depending on that account's permissions, the malicious dependency could access readable project files, environment variables, credentials, us ...[truncated 339 chars]
- A user or automated agent follows the installation instruction in
- Remediation
View remediation
Remediation Suggestions
-
Replace implicit latest-version resolution with an exact, audited version, for example:
yaml install: "npx --yes clawhub@<audited-exact-version> install howtousehumans/emotional-regulation" -
Verify the selected package release against trusted provenance and integrity information before publishing the installation instruction.
-
Use a lockfile and registry-provided integrity hashes where the surrounding installation workflow supports them.
-
Prefer a locally installed, reviewed CLI invoked through a package-manager script instead of downloading executable code at installation time.
-
Restrict installation to a trusted registry and consider allowlisting the expected package name, version, publisher, and artifact digest.
-
Run installation with least privilege in an isolated environment without unnecessary credentials or access to sensitive host paths.
-
Disable dependency lifecycle scripts where operationally possible, while recognizing that this does not prevent malicious behavior in the invoked CLI itself.
-
