T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Global Installation of an Unreviewed Third-Party Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13–21 and line 31
Vulnerability Type: Third-party supply-chain exposure through a mutable npm dependency
Risk Level: MediumVulnerable Code
yaml "install": [ { "id": "npm", "kind": "node", "package": "@shan8851/blackbox", "bins": ["blackbox"], "label": "Install OpenClaw Blackbox (npm)", }, ],markdown - `npm install -g @shan8851/blackbox`Technical Analysis
The skill delegates all operational behavior to the external npm package
@shan8851/blackbox, but the reviewed project contains neither that package's implementation nor a lockfile, exact version, or integrity hash. Consequently, the effective executable payload cannot be verified from the audited artifact and may change after this review.The documented
npm install -gcommand installs the package globally. npm installation may execute package lifecycle scripts, while the installedblackboxbinary subsequently runs with the invoking user's permissions. An unpinned dependency can resolve to a newer or compromised release without any corresponding change to this skill.The audit did not establish that the referenced package is malicious. The vulnerability is the unsafe and unverifiable supply-chain trust model.
Attack Path
- An attacker compromises the npm package, its publisher account, or a transitive dependency.
- The attacker publishes a modified release containing malicious lifecycle or runtime code.
- A user follows the skill instructions and runs
npm install -g @shan8851/blackbox. - npm resolves the mutable package reference to the compromised release.
- Malicious lifecycle code may execute during installation, or malicious code executes when the user invokes
blackbox. - The code operates with the installing or invoking user's permissions and may access files available to that account.
...[truncated 548 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the package to a specific, reviewed version rather than installing the latest mutable release.
- Use a lockfile and verify the package archive against a trusted integrity hash.
- Include or link to the exact source revision corresponding to the pinned package release.
- Review the package and its transitive dependencies before distribution.
- Prefer a project-local, isolated installation instead of a global installation.
- Disable npm lifecycle scripts during installation where operationally feasible, and explicitly review any lifecycle scripts that are required.
- Execute the CLI in a sandbox with narrowly scoped filesystem access and without unrelated credentials in its environment.
- Establish dependency monitoring and a controlled update process so package upgrades require a new security review.
