T08 · Insecure Dependencies
- Location
SKILL.md:78- Finding
Unpinned Global Installation of a Security-Sensitive Third-Party CLI
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:78
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code Snippet:
markdown 1. **RunComfy CLI**: `npm i -g @runcomfy/cli`Technical Analysis
The Skill instructs users to install the latest available version of
@runcomfy/cliglobally without specifying an exact version or verifying package integrity or provenance. Consequently, the code installed and executed can change after this Skill has been reviewed.This dependency is security-sensitive because the documented workflow gives the CLI access to the RunComfy bearer token, user prompts, image references, generated files, and output directories. The project contains no lockfile, checksum, vendored implementation, or other mechanism for independently verifying the installed CLI version. Its documented network restrictions and token-handling behavior therefore cannot be validated from this repository.
Global installation also increases exposure by placing the package in the user's shared tool environment. npm package installation may execute package lifecycle scripts with the privileges of the user running npm, while subsequent CLI execution operates with that user's filesystem and environment access.
Attack Path
- An attacker compromises the npm package, its publisher account, or a future package release.
- The malicious release becomes the version resolved by the unpinned
npm i -g @runcomfy/clicommand. - A user follows the Skill's prerequisite instructions and globally installs the package.
- Malicious lifecycle or runtime code executes with the installing user's privileges.
- The compromised CLI may read accessible environment variables or configuration files, including
RUNCOMFY_TOKENor~/.config/runcomfy/token.json. - During normal Skill use, it may intercept prompts, image URLs, generated content, or modify network reque ...[truncated 949 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a reviewed exact version, for example:
bash npm install --global @runcomfy/cli@<reviewed-exact-version> - Document the expected npm publisher, package provenance, and integrity hash.
- Prefer a project-local installation with a committed lockfile instead of modifying the user's global npm environment.
- Verify npm registry provenance or signatures before installation and monitor the dependency for publisher or ownership changes.
- Disable npm lifecycle scripts during installation where compatible with the package's documented installation process.
- Run the CLI under a dedicated, least-privileged account or isolated container with access only to required output directories.
- Provide the RunComfy token only for the duration of the command and avoid exposing unrelated secrets in the same environment.
- Independently review and document the pinned CLI's actual outbound endpoints, token storage, download validation, and file-size controls rather than relying solely on behavioral claims in
SKILL.md.
- Pin the CLI to a reviewed exact version, for example:
