T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:15
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
yaml install: "npx clawhub install stoicism-daily-practice"Technical Analysis
The installation instruction invokes
clawhubthroughnpxwithout specifying an exact package version, integrity hash, lockfile, or trusted registry. Depending on the local npm configuration and cache state,npxcan retrieve and execute the package version currently resolved by the configured registry.This makes the code executed during installation mutable after the Skill has been reviewed. If the
clawhubpackage, its publishing account, one of its transitive dependencies, or the configured registry is compromised, installation could execute attacker-controlled package code. The reviewed project does not itself contain an embedded malicious script, so this finding concerns supply-chain exposure rather than confirmed malicious behavior.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, a transitive dependency, or a registry used by the victim. - The attacker publishes or serves a malicious version that satisfies the unversioned package request.
- A user or automated system follows the documented installation command.
npxresolves and downloads the attacker-controlled package or dependency.- Package lifecycle hooks or CLI entry-point code execute with the privileges of the user running the command.
- The malicious code can perform any operation permitted to that user.
Impact Assessment
Successful exploitation permits arbitrary code execution in the installation process under the invoking user's operating-system privileges. Potential scope includes reading or modifying files accessible to that account, accessing environment variables and locally available credentials, altering project files, and making network requests ...[truncated 227 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to an explicitly reviewed version, for example by using
npx clawhub@<exact-version> .... - Use a lockfile and verify package integrity through registry integrity metadata or independently published checksums.
- Explicitly configure and document the trusted npm registry rather than relying on ambient user configuration.
- Review the pinned package, its lifecycle scripts, and its complete transitive dependency tree before approving installation.
- Prefer installing dependencies in a restricted environment and invoke a locally pinned binary rather than dynamically downloading and executing the latest package.
- Run installation with least privilege, without administrator rights, production credentials, or unnecessary access to sensitive directories.
- Pin the installer to an explicitly reviewed version, for example by using
