T08 · Insecure Dependencies
- Location
SKILL.md:78- Finding
Unpinned Globally Installed Third-Party CLI
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:78
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
markdown 1. **RunComfy CLI** — `npm i -g @runcomfy/cli`Technical Analysis
The installation instruction retrieves the latest available version of
@runcomfy/clifrom the configured npm registry and installs it globally without pinning a reviewed version or verifying package integrity.The CLI is subsequently entrusted with the
RUNCOMFY_TOKEN, user-provided prompts, outbound network access, and write access to the selected output directory. A compromised package release, npm account, registry response, or dependency in the package's transitive dependency tree could therefore introduce arbitrary install-time or runtime behavior after this Skill has been reviewed.Global installation also makes the executable available beyond this Skill's immediate execution context and increases the scope of a supply-chain compromise. The audit did not find evidence that the named package is currently malicious; the vulnerability is the mutable and unverified dependency installation process.
Attack Path
- An attacker compromises the npm package, its publisher account, or a transitive dependency and publishes a malicious release.
- A user follows the documented
npm i -g @runcomfy/cliinstruction, which resolves to the compromised latest version. - npm executes any package lifecycle scripts with the installing user's privileges and installs the CLI globally.
- The malicious package can access data available to the user during installation or later execution.
- When invoked, the CLI can read the RunComfy token, inspect submitted prompts, alter network requests, write arbitrary files within user-accessible locations, or transmit accessible information to an attacker-controlled endpoint.
Impact Assessment
Successful exploitation would provide code execution with the privileges of the user who i ...[truncated 522 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin the CLI to a specifically reviewed version, for example:
bash npm install --global @runcomfy/cli@<reviewed-version> -
Publish and verify the expected package version, registry origin, package digest, and provenance before installation.
-
Prefer a project-local dependency with a committed lockfile over global installation, then invoke it through a controlled package script or an equivalent version-pinned mechanism.
-
Disable npm lifecycle scripts during installation if the package does not require them, and separately review any required install scripts.
-
Review the pinned package and its transitive dependencies before upgrades. Document a controlled update process rather than automatically consuming the latest release.
-
Run the CLI with least privilege in an isolated environment, exposing only the required RunComfy credential and output directory.
-
Use a narrowly scoped, revocable API token and avoid exposing unrelated secrets through the process environment.
-
