T08 · Insecure Dependencies
Warning
- Location
SKILL.md:9- Finding
Mutable Third-Party Package Is Executed Through an Unpinned Latest Tag
- Content
View full analysis
`npx clawhub@latest install deepseekoracle/lygo-champion-council` ``` ### Technical Analysis The documented installation command instructs users to execute the `latest` release of the third-party `clawhub` npm package through `npx`. The `latest` tag is mutable and may resolve to different package contents over time. The project does not pin an audited package version or specify an integrity digest. Because `npx` downloads and executes package code, the command crosses a supply-chain trust boundary. The reviewed repository does not establish that the package version executed by a future user is the same version reviewed or expected by the project. No evidence was found that the current upstream package is malicious. The vulnerability is the use of an unauthenticated, mutable dependency in an executable installation instruction. ### Attack Path 1. An attacker compromises the upstream npm package, its publisher account, or the mutable `latest` release channel. 2. The attacker publishes a modified release and assigns it to the `latest` tag. 3. A user follows the installation command in `SKILL.md`. 4. `npx` resolves, downloads, and executes the attacker-controlled release. 5. The payload runs with the privileges and environment access of the invoking user. ### Impact Assessment Successful exploitation could permit arbitrary code execution under the invoking user's account. Depending on that account's privileges and environment, the payload could access user-readable files, credentials exposed to the process, project data, and network resources. If the command is run with elevated privileges, the scope could extend to system-wide resources. The issue does not independently provide elevated privileges; its maximum scope is determined by the privileges granted to the `npx` proces ...[truncated 6 chars]- Remediation
View remediation
install deepseekoracle/lygo-champion-council ``` 2. Pin and verify the package integrity digest through a lockfile or another authenticated package-verification mechanism. 3. Document the expected publisher, registry, exact version, and integrity value. 4. Review a new package version before updating the documented command. 5. Where practical, download and inspect the package before executing it, and run installation with the minimum required privileges in an isolated environment. ]]>