T08 · Insecure Dependencies
- Location
README.md:25- Finding
Unpinned Third-Party Code Execution During Installation
- Content
View full analysis
Vulnerability Details
File Locations:
README.md:25-32SKILL.md:21-23
Vulnerability Type: Unpinned and mutable third-party dependencies executed through
npx
Risk Level: MediumVulnerable Code
README.md:25-32:bash npx add https://github.com/wpank/ai/tree/main/skills/meta/workflow-patternsbash npx clawhub@latest install workflow-patternsSKILL.md:21-23:bash npx clawhub@latest install workflow-patternsTechnical Analysis
The documented installation commands instruct users to execute third-party content using
npx. If a requested package is not already available locally,npxcan retrieve and execute it, including its command-line entry point and potentially package lifecycle scripts.The
clawhub@latestdependency uses a mutable version selector rather than an audited, exact version. The GitHub-based command similarly references remote repository content without pinning it to a reviewed commit hash or verifying its integrity. Consequently, the code executed when a user follows these instructions can differ from the code available when this project was audited.This does not establish that either current upstream source is malicious. The vulnerability is the lack of controls preventing a compromised registry account, package release, repository, branch, or transitive dependency from supplying altered executable content.
Attack Path
- An attacker compromises the package publisher, package registry account, upstream repository, mutable release channel, or a dependency used by the installer.
- The attacker publishes malicious code under the version resolved by
@latestor changes the remotely referenced repository content. - A user follows one of the documented
npxinstallation commands. npxdownloads the altered package or installer from the external source.- The downloaded CLI code or package lif ...[truncated 1052 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace
clawhub@latestwith an exact, reviewed package version:bash npx clawhub@<reviewed-exact-version> install workflow-patterns -
Pin GitHub-hosted content to an immutable, reviewed commit hash rather than a mutable branch or repository path.
-
Publish and verify cryptographic checksums or signed release artifacts before installation.
-
Prefer a download, verification, and review workflow over immediately executing remotely resolved content.
-
Use lockfiles and package-manager integrity metadata for all direct and transitive dependencies where supported.
-
Document that installation should be performed without administrative privileges and in an isolated development environment.
-
Add an automated release process that verifies dependency provenance, signatures, integrity hashes, and the exact source revision associated with each documented installation command.
-
