T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:32
- Finding
- Unpinned Package Execution During Installation## Vulnerability Details **File Location**: `SKILL.md:32-36`; duplicated in `README.md:24-28` **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: Medium ### Vulnerable Code `SKILL.md:32-36`: ```bash ## Installation ```bash npx clawhub install tokenguard-pro ``` ``` `README.md:24-28`: ```bash ## Installation ```bash npx clawhub install tokenguard-pro ``` ``` ### Technical Analysis The documented installation procedure invokes `clawhub` through `npx` without specifying a package version or verifying its integrity. If the package is not already available locally, `npx` can retrieve the current package release from the configured npm registry and execute it immediately. Because neither an exact version nor an integrity hash is supplied, the code executed by this command may differ from the code that existed when the Skill was audited. This creates a supply-chain trust dependency on the npm package, registry configuration, publisher account, and all transitive components used by the retrieved package. The artifact also contains no lockfile or other mechanism that would make this installation command reproducible. This finding does not establish that the current `clawhub` package is malicious; it identifies an unsafe, mutable execution path that could become exploitable following package compromise, malicious publication, dependency confusion, or registry redirection. Additionally, the supplied artifact does not contain the `tokenguard-analyze` executable referenced by `package.json` and `clawhub.yaml`. Therefore, its advertised runtime behavior could not be audited from the provided files. This missing file is an audit limitation rather than evidence that malicious code exists. ### Attack Path 1. An attacker compromises the publisher account, registry package, package dependency chain, or the user's npm registry configuration. 2. The attacker publishes or serves a modified `c ...[truncated 1196 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the installer to a specifically reviewed release: ```bash npx --yes clawhub@X.Y.Z install tokenguard-pro ``` 2. Document the expected official npm registry and package publisher so users can verify package provenance before execution. 3. Publish and document an expected package integrity digest or signed release artifact. 4. Prefer a verified, locally installed installer over an implicit download-and-execute workflow. 5. Use lockfiles and exact versions for all development and installation dependencies where applicable. 6. Advise users to run installation with a non-privileged account and not to use `sudo`. 7. Add the missing `tokenguard-analyze` executable to the reviewed package so the installed behavior can be inspected before release. 8. Ensure `package.json`, `clawhub.yaml`, and the distributed archive contain the same reviewed files and versions.