T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:10
- Finding
- Unpinned npm Dependency Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md`, line 10 **Vulnerability Type**: Unpinned third-party npm dependency **Risk Level**: Medium ### Vulnerable Code ```yaml metadata: {"openclaw":{"emoji":"☁️","requires":{"bins":["mcporter"]},"install":[{"id":"npm","kind":"node","package":"mcporter","bins":["mcporter"],"label":"Install mcporter (npm)"}]}} ``` ### Technical Analysis The installation metadata references the `mcporter` npm package without specifying an exact reviewed version or an integrity hash. Consequently, installation resolves whichever package version is selected by the npm registry at installation time. The installed code can therefore differ from the code that was available when this Skill was audited. This mutable dependency resolution creates a supply-chain exposure. If the package publisher account, npm package, registry response, or a transitive dependency is compromised, an attacker-controlled release could be installed. npm lifecycle scripts may execute during installation, and malicious runtime logic could execute when the Skill invokes the resulting `mcporter` binary. The project contains no evidence that `mcporter` is currently malicious. The vulnerability is the absence of controls that ensure installation reproduces a specifically reviewed dependency artifact. ### Attack Path 1. An attacker compromises the `mcporter` package, its publisher account, or one of its transitive dependencies and publishes a malicious release. 2. A user installs the Skill after the malicious release becomes resolvable from npm. 3. Because the package declaration does not pin an exact version or integrity value, the installation process retrieves the attacker-controlled artifact. 4. Malicious lifecycle code may execute during package installation, or malicious runtime code may execute when the Agent calls the `mcporter` binary. 5. The payload operates with the privileges of the account running the installation or command and can access resource ...[truncated 676 chars]
- Remediation
- ## Remediation Suggestions 1. Pin `mcporter` to an exact, reviewed version rather than allowing mutable version resolution. 2. Use a lockfile that records exact transitive dependency versions and commit it to the reviewed project where the installation framework supports lockfiles. 3. Verify dependency artifacts using npm integrity metadata, registry provenance, signatures, or an equivalent trusted checksum mechanism. 4. Review the selected package version and its transitive dependency tree before deployment. 5. Disable npm lifecycle scripts during installation where operationally feasible, and explicitly review any scripts that must remain enabled. 6. Install and execute the tool in a restricted environment with minimal filesystem, credential, and network access. 7. Use a trusted registry or internal package mirror with package allowlisting and malware scanning. 8. Monitor dependency advisories and perform controlled upgrades only after reviewing and testing each new version.