T08 · Insecure Dependencies
Warning
- Location
SKILL.md:80- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 80-83
Vulnerability Type: Unpinned third-party installer execution
Risk Level: MediumComplete Code Snippet:
markdown **1. Install the skill:** ```bash npx clawhub@latest install chain-senseitext ### Technical Analysis The installation instructions invoke `clawhub` through `npx` using the mutable `@latest` distribution tag. If the package is not already available locally, `npx` can retrieve it from the configured package registry and execute it with the invoking user's permissions. Because `@latest` does not identify an immutable, reviewed release, the code executed by this command may change after this skill has been audited. The project does not provide an exact dependency version, integrity hash, lockfile, vendored installer, or other mechanism for verifying that the retrieved package matches a trusted artifact. This is a supply-chain weakness rather than evidence that the current `clawhub` package is malicious. The same unsafe command also appears in `README.md` at lines 5-9, increasing the likelihood that users will follow it. ### Attack Path 1. An attacker compromises the registry account, publication pipeline, or another distribution component used to publish `clawhub`. 2. The attacker publishes a malicious release and assigns it to the mutable `latest` tag. 3. A user follows the documented `npx clawhub@latest install chain-sensei` instruction. 4. `npx` downloads the attacker-controlled package from the configured registry. 5. The retrieved package executes with the permissions and environment available to the user running the installation. 6. The malicious package can perform any operation permitted to that user before or during installation. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the invoking user's account. Depending on that account's privileges and environment, the d ...[truncated 549 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, security-reviewed package version. - Verify the downloaded package using registry integrity metadata or a documented cryptographic checksum.
- Record installation dependencies in a lockfile where the surrounding package-management workflow supports it.
- Document the expected registry and reject untrusted registry overrides.
- Prefer an installation process that separates package download and verification from execution.
- Run the installer with a minimally privileged account in a sandbox or isolated environment without unnecessary credentials.
- Keep the installation command in
README.mdandSKILL.mdsynchronized, applying the same pinned and verified version in both locations. - Review each new installer release before updating the pinned version.
- Replace