T08 · Insecure Dependencies
- Location
references/installation-flow.md:23- Finding
Unpinned Global Installation of an Unreviewed npm Package
- Content
View full analysis
Vulnerability Details
File Location:
references/installation-flow.md:23-28
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: HighComplete Code Snippet:
bash npm install -g opclawtmA secondary installation path also uses an alternative registry:
bash npm install -g opclawtm --registry=https://registry.npmmirror.comTechnical Analysis
The Skill instructs the agent to install the latest available version of
opclawtmglobally without specifying an exact version or validating package integrity. npm installation can execute package lifecycle scripts, includingpreinstall,install, andpostinstall. Consequently, code absent from this audited repository may run on the host during installation.Global installation increases the effect of a compromised dependency by placing executables in a system-wide or user-wide command path. The accompanying instructions also recommend administrator privileges when permission errors occur, which could cause lifecycle scripts to execute with elevated operating-system permissions.
The fallback to
registry.npmmirror.comcreates an additional supply-chain trust boundary. The repository contains no lockfile, checksum, signature, package provenance verification, or source code for the installed CLI.Attack Path
- An attacker compromises the
opclawtmnpm package, its publisher account, a transitive dependency, or a registry distribution path. - The attacker publishes a modified version containing a malicious npm lifecycle script or CLI executable.
- A user or agent follows the Skill and runs the unpinned global installation command.
- npm downloads the attacker-controlled current version and executes its lifecycle scripts.
- If the installation is run with administrator privileges as suggested by the documentation, the payload inherits those elevated privileges.
- The installed executable remain ...[truncated 614 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed exact version, such as
opclawtm@X.Y.Z. - Record and verify the package integrity hash before installation.
- Use the official npm registry unless an alternative registry has been formally assessed and approved.
- Publish or vendor the CLI source and its dependency lockfile so its runtime behavior can be audited.
- Verify npm provenance signatures and publisher identity in an automated installation wrapper.
- Avoid global installation where possible. Install into an isolated project, container, or restricted service account.
- Do not recommend administrator privileges as a generic response to installation failures.
- Disable lifecycle scripts during initial inspection with
npm install --ignore-scripts, inspect the package, and only permit required scripts after review.
- Pin the dependency to a reviewed exact version, such as
