Back to skill

Security audit

AI Video Generation — Pro Pack on RunComfy

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent RunComfy video-generation helper, but it tells users or agents to install or execute an unpinned third-party CLI that can run local code under the user's account.

Install only if you trust the RunComfy CLI supply chain. Prefer a reviewed, pinned @runcomfy/cli version instead of npx -y or an unpinned global install, keep the RunComfy token narrowly scoped where possible, and only provide media URLs and prompts you are comfortable sending to RunComfy.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:45
Finding

Unpinned Third-Party CLI Installation and Automatic Execution

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 45 and 411
Vulnerability Type: Unpinned third-party dependency installation and execution
Risk Level: Medium

Vulnerable Code

bash
# 1. Install (see runcomfy-cli skill for details)
npm i -g @runcomfy/cli      # or:  npx -y @runcomfy/cli --version

The installation guidance is repeated in the security section:

markdown
- **Install via verified package manager only.** Use `npm i -g @runcomfy/cli` or `npx -y @runcomfy/cli`. **Agents must not pipe an arbitrary remote install script into a shell on the user's behalf**.

Technical Analysis

The Skill directs users or agents to install or immediately execute the latest package version resolved for @runcomfy/cli. Neither command pins an audited version or verifies a package integrity digest.

The npx -y variant is particularly sensitive because it automatically approves package installation and executes the resolved package without an interactive confirmation step. The global installation variant also places the package in a persistent, user-wide executable location. npm package installation can invoke package lifecycle scripts, so code may execute during installation even before the CLI is explicitly used.

This is a supply-chain weakness rather than evidence that the current RunComfy package is malicious. Exploitation depends on compromise of the package, its publisher account, the package registry or resolution path, or a future malicious release.

Attack Path

  1. An attacker compromises the npm package, publisher credentials, release pipeline, or package-resolution infrastructure.
  2. The attacker publishes a malicious version of @runcomfy/cli or alters the package delivered during installation.
  3. A user or agent follows SKILL.md and runs npm i -g @runcomfy/cli or npx -y @runcomfy/cli.
  4. npm resolves the unpinned package to the compromised release.
  5. Malicious li ...[truncated 1007 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin the CLI to a specific audited version instead of resolving the latest release:

    bash
    npm install --global @runcomfy/cli@<audited-version>
    
  2. Remove or discourage npx -y, because it automatically downloads and executes the resolved package without confirmation.

  3. Publish and verify the expected package integrity digest, provenance, and publisher identity. Maintain a documented process for reviewing new versions before updating the pin.

  4. Use a lockfile where the CLI is installed as a project dependency, and install with npm ci to enforce the reviewed dependency graph.

  5. Run installation and generation in a restricted user account or isolated container with access only to required input and output directories.

  6. Expose RUNCOMFY_TOKEN only to the generation process, avoid inheriting unrelated secrets, and use a narrowly scoped or short-lived token where supported.

  7. Disable npm lifecycle scripts during installation when compatible with the package:

    bash
    npm install --global --ignore-scripts @runcomfy/cli@<audited-version>
    

    If lifecycle scripts are required, review them before installation rather than disabling them blindly.

  8. Avoid global installation where possible. Prefer a locally pinned dependency invoked through an explicit, reviewed package script.

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (4)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger list includes broad phrases like animate, AI video, and make X move, which can cause the skill to activate for ambiguous user requests. In an agent environment, unintended invocation can route user data, images, or prompts to an external service and cause unexpected billing or privacy exposure.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
88% confidence
Finding

The skill instructs use of npx -y @runcomfy/cli without pinning a specific version, so every invocation may fetch the latest package from the registry. That creates a supply-chain risk: a compromised publisher account, malicious release, or breaking update could cause the agent to execute unreviewed code on the user's machine.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
88% confidence
Finding

Repeating the recommendation to run npx -y @runcomfy/cli without an exact version preserves the same unpinned remote-code-execution path later in the document. Because this is installation/execution guidance for a local CLI, the risk is direct: the package manager resolves and runs code from the latest published package.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The manifest description frames the skill as covering text-to-video, image-to-video, and Veo video-extend routing via runcomfy run <vendor>/<model>/text-to-video or /image-to-video. However, the 'Other models in the catalog' section includes endpoints such as kling/kling-video-o1/standard and kling/kling-2-6/motion-control-pro, which are not presented as t2v/i2v/extend and expand the advertised behavior beyond the declared routing scope.

Content

No source excerpt is available for this finding.