T08 · Insecure Dependencies
- Location
SKILL.md:71- Finding
Unpinned Third-Party CLI Installation and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 71
Vulnerability Type: Unpinned third-party dependency and unsafe package execution
Risk Level: MediumVulnerable Code Snippet
markdown 1. **RunComfy CLI** — `npm i -g @runcomfy/cli` (or `npx -y @runcomfy/cli --version`)Technical Analysis
The Skill instructs users to install or execute
@runcomfy/cliwithout specifying a reviewed version or verifying package integrity. Both commands resolve a mutable package version from the npm registry:npm i -g @runcomfy/cliinstalls the package globally and may execute npm lifecycle scripts.npx -y @runcomfy/cli --versionautomatically downloads and executes the resolved package without interactive confirmation.
Because the package version is not pinned, the code executed by users can change after this Skill has been reviewed. A compromised publisher account, malicious package release, registry compromise, or unexpected upstream change could therefore introduce arbitrary code into the workflow.
The global installation recommendation also unnecessarily broadens persistence and exposure compared with a project-local, version-pinned installation. The CLI implementation is not included in the audited project, so its behavior and the claims made elsewhere in
SKILL.md—including endpoint restrictions, token handling, download limits, and absence of telemetry—cannot be independently verified from this artifact.Attack Path
- An attacker compromises the npm publisher account, release pipeline, or another component used to distribute
@runcomfy/cli. - The attacker publishes a malicious release under the legitimate package name.
- A user follows the Skill instructions and runs either
npm i -g @runcomfy/cliornpx -y @runcomfy/cli --version. - npm resolves the unpinned dependency to the malicious release.
- Malicious lifecycle scripts or package code execute with the privileges of t ...[truncated 1449 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin the CLI to an explicitly reviewed version, for example:
bash npx --yes @runcomfy/cli@<reviewed-version> --version -
Publish and verify the expected npm package integrity hash or signed release provenance before execution.
-
Prefer a project-local dependency with a committed lockfile over a global installation.
-
Avoid recommending installation with elevated privileges.
-
Disable npm lifecycle scripts where compatible with the package:
bash npm install --ignore-scripts --save-exact @runcomfy/cli@<reviewed-version>If lifecycle scripts are required, document and review them before installation rather than disabling them blindly.
-
Run the CLI in a constrained environment with access only to the required output directory and RunComfy credential.
-
Provide a link to the official package repository and documented release-verification process.
-
Re-audit the pinned CLI whenever the documented version changes.
-
