T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:720
- Finding
- Unpinned Third-Party Package Execution Through npx## Vulnerability Details **File Location**: `SKILL.md`, lines 720 and 733 **Vulnerability Type**: Insecure third-party dependency execution **Risk Level**: Medium ### Vulnerable Code Line 720: ```bash npx clawhub install tender-bidding-assistant@3.2.2 ``` Line 733: ```markdown **Install**: `npx clawhub install tender-bidding-assistant@3.2.2` ``` ### Technical Analysis The installation instructions pin the skill version to `3.2.2`, but they do not pin the version of the npm-distributed `clawhub` executable. When the command is invoked, `npx` may download and execute the package version currently resolved by the npm registry. The downloaded package and its potential lifecycle behavior are not included in this project, so their integrity and behavior cannot be established by this audit. Pinning the skill version does not protect the execution path from an altered, compromised, or unexpectedly updated `clawhub` package. This is a supply-chain weakness rather than evidence that the current artifact is itself malicious. ### Attack Path 1. An attacker compromises the npm publication account, package, or relevant dependency used by `clawhub`. 2. A user follows the documented installation command. 3. `npx` resolves and downloads the current unpinned `clawhub` package. 4. The downloaded package or its dependency lifecycle code executes with the invoking user's permissions. 5. Malicious code could access resources available to that user or modify the local environment. Exploitation depends on compromise or malicious modification of the external package supply chain. ### Impact Assessment Successful exploitation could provide code execution under the privileges of the user running the installation command. Depending on that user's permissions and environment, the affected scope could include: - Reading or modifying user-accessible files. - Accessing environment variables and locally available credentials. - Altering the working directory or user-level conf ...[truncated 228 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the `clawhub` executable to an exact, reviewed version: ```bash npx clawhub@<reviewed-exact-version> install tender-bidding-assistant@3.2.2 ``` 2. Record and verify the package integrity hash or lockfile metadata before execution. 3. Prefer a separately installed and reviewed CLI rather than allowing `npx` to perform an implicit download at invocation time. 4. Use a trusted internal registry or approved package mirror where appropriate. 5. Run installation in a restricted environment without sensitive credentials and with minimum filesystem and network permissions. 6. Document package provenance and a process for verifying that installed package contents match the reviewed source. 7. Consider disabling unnecessary npm lifecycle scripts during installation when compatible with the package.