Back to skill

Security audit

HappyHorse 1.0 — Pro Pack on RunComfy

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed RunComfy wrapper for generating HappyHorse text-to-video outputs, with ordinary credential and network requirements for that purpose.

Before installing, consider using a pinned or project-local @runcomfy/cli version, verify the package source, and use a narrowly scoped RunComfy token. Prompts and generated results are sent to and retrieved from RunComfy, so avoid submitting sensitive content unless that fits your account and data-handling expectations.

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: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: Medium

Vulnerable Code

markdown
1. **RunComfy CLI** — `npm i -g @runcomfy/cli`

Technical Analysis

The installation instruction retrieves the latest available version of @runcomfy/cli from 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

  1. An attacker compromises the npm package, its publisher account, or a transitive dependency and publishes a malicious release.
  2. A user follows the documented npm i -g @runcomfy/cli instruction, which resolves to the compromised latest version.
  3. npm executes any package lifecycle scripts with the installing user's privileges and installs the CLI globally.
  4. The malicious package can access data available to the user during installation or later execution.
  5. 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

  1. Pin the CLI to a specifically reviewed version, for example:

    bash
    npm install --global @runcomfy/cli@<reviewed-version>
    
  2. Publish and verify the expected package version, registry origin, package digest, and provenance before installation.

  3. 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.

  4. Disable npm lifecycle scripts during installation if the package does not require them, and separately review any required install scripts.

  5. Review the pinned package and its transitive dependencies before upgrades. Document a controlled update process rather than automatically consuming the latest release.

  6. Run the CLI with least privilege in an isolated environment, exposing only the required RunComfy credential and output directory.

  7. Use a narrowly scoped, revocable API token and avoid exposing unrelated secrets through the process environment.

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep