T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned npm Dependency Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 10
Vulnerability Type: Unpinned third-party npm dependency
Risk Level: MediumVulnerable 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
mcporternpm 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
mcporterbinary.The project contains no evidence that
mcporteris currently malicious. The vulnerability is the absence of controls that ensure installation reproduces a specifically reviewed dependency artifact.Attack Path
- An attacker compromises the
mcporterpackage, its publisher account, or one of its transitive dependencies and publishes a malicious release. - A user installs the Skill after the malicious release becomes resolvable from npm.
- Because the package declaration does not pin an exact version or integrity value, the installation process retrieves the attacker-controlled artifact.
- Malicious lifecycle code may execute during package installation, or malicious runtime code may execute when the Agent calls the
mcporterbinary. - The payload operates with the privileges of the account running the installation or command and can access resource ...[truncated 676 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
mcporterto an exact, reviewed version rather than allowing mutable version resolution. - Use a lockfile that records exact transitive dependency versions and commit it to the reviewed project where the installation framework supports lockfiles.
- Verify dependency artifacts using npm integrity metadata, registry provenance, signatures, or an equivalent trusted checksum mechanism.
- Review the selected package version and its transitive dependency tree before deployment.
- Disable npm lifecycle scripts during installation where operationally feasible, and explicitly review any scripts that must remain enabled.
- Install and execute the tool in a restricted environment with minimal filesystem, credential, and network access.
- Use a trusted registry or internal package mirror with package allowlisting and malware scanning.
- Monitor dependency advisories and perform controlled upgrades only after reviewing and testing each new version.
- Pin
