T08 · Insecure Dependencies
- Location
SKILL.md:50- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:50
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumComplete Code Snippet
markdown 1. **RunComfy CLI** — `npm i -g @runcomfy/cli`Technical Analysis
The prerequisite installs the latest available release of
@runcomfy/cliglobally without pinning a reviewed version or verifying its integrity. Because the npm package reference is mutable, the code installed when a user follows this instruction may differ from the version that existed when the Skill was audited.npm installation may execute package lifecycle scripts, and the installed CLI later processes authentication tokens, prompts, image URLs, output files, and network responses. A compromise of the package, its publisher account, or its dependency chain could therefore introduce arbitrary local behavior. The global installation scope also makes the CLI available outside this Skill and increases the duration and breadth of exposure.
This does not establish that the current package is malicious. The vulnerability is the unsafe, unpinned supply-chain trust model prescribed by the Skill.
Attack Path
- An attacker compromises the
@runcomfy/clipackage, its publisher account, or a transitive dependency used by a future release. - The attacker publishes a malicious package version under the legitimate package name.
- A user follows
SKILL.md:50and runsnpm i -g @runcomfy/cli. - npm resolves the mutable package reference to the compromised release.
- Malicious lifecycle scripts may execute during installation, or malicious code may execute when the CLI is invoked.
- The payload operates with the privileges of the installing or invoking user and may access data available to that process.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the current user's privileges. Depending on the user's enviro ...[truncated 483 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version, for example
@runcomfy/cli@<approved-version>. - Prefer a project-local dependency governed by a committed lockfile instead of a global installation.
- Use npm integrity and provenance verification controls and document the expected package publisher and registry.
- Review the pinned package's lifecycle scripts and transitive dependencies before recommending installation.
- Run the CLI under a minimally privileged account or isolated environment with access only to required inputs, outputs, and credentials.
- Establish an explicit dependency-update process that requires security review before changing the pinned version.
- Pin the CLI to a specifically reviewed version, for example
