T08 · Insecure Dependencies
- Location
SKILL.md:99- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 99
Vulnerability Type: Unpinned third-party dependency and supply-chain exposure
Risk Level: MediumVulnerable Code:
bash npm i -g @runcomfy/cliTechnical Analysis
The Skill instructs users to install the latest available version of
@runcomfy/cliglobally. It does not specify a reviewed version, lock an integrity hash, or provide a provenance-verification procedure.npm packages can execute lifecycle scripts during installation. Consequently, a compromised or unexpectedly modified package release could execute code with the privileges of the user running npm. The CLI also operates in a context where it can access the RunComfy authentication token, RunComfy configuration, submitted image URLs, and generated files.
This is a supply-chain risk rather than evidence that the current RunComfy package is malicious. The effective installation payload can change after the Skill itself has been audited because the command resolves the package version at execution time.
Attack Path
- An attacker compromises the upstream npm package, its publisher account, or a future package release.
- The attacker publishes a malicious version under the legitimate package name.
- A user follows the Skill instructions and runs
npm i -g @runcomfy/cli. - npm retrieves the latest release and may execute attacker-controlled lifecycle scripts during installation.
- The installed package can execute with the invoking user's privileges.
- When subsequently used, the malicious CLI can access
RUNCOMFY_TOKEN, local RunComfy configuration, user-provided image URLs, generated files, and other files available to that user.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the invoking user's privileges. The attacker could steal the RunComfy token, inspect or modify user-accessible files, alter generated artifacts, o ...[truncated 284 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to an explicitly reviewed version, for example:
bash npm install --global @runcomfy/cli@<reviewed-version> - Publish and verify the expected package integrity digest or npm provenance before installation.
- Prefer a project-local installation with a committed lockfile over a global installation.
- Disable npm lifecycle scripts during installation where compatible:
bash npm install --ignore-scripts --save-exact @runcomfy/cli@<reviewed-version> - Document the expected package publisher, registry, version, and checksum so users can identify dependency confusion or package substitution.
- Run the CLI under a minimally privileged account and expose
RUNCOMFY_TOKENonly for the duration of the required API call. - Periodically review and deliberately update the pinned version rather than implicitly accepting every upstream release.
- Pin the CLI to an explicitly reviewed version, for example:
