Back to skill

Security audit

AI Music — Pro Pack on RunComfy

Security checks for vulnerabilities and agentic risk

Overview

This music-generation skill is coherent, but it asks users or agents to install and run an unpinned external CLI that handles account tokens and can make billable network calls.

Review this skill before installing. Use a pinned, reviewed version of the RunComfy CLI where possible, avoid unattended `npx -y` execution, run it with only the files and environment variables it needs, and expect prompts, lyrics, audio URLs, and generated outputs to be processed through RunComfy with possible account charges.

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:41
Finding

Unpinned npm CLI Installation and Execution

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 41–42
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: Medium

Vulnerable Code:

bash
npm i -g @runcomfy/cli                              # global install
npx -y @runcomfy/cli --version                      # zero-install

Technical Analysis

The skill instructs operators or agents to install and execute @runcomfy/cli without specifying an exact reviewed version or verifying package integrity. Both commands resolve mutable content from the npm registry. In particular, npx -y can download and execute the currently resolved package without interactive confirmation.

The implementation of @runcomfy/cli is not included in this project and was therefore outside the auditable code boundary. npm packages can execute code through package lifecycle scripts and CLI entry points. Consequently, a compromised maintainer account, malicious package release, registry compromise, or unexpected future release could introduce arbitrary code after this skill has already been reviewed.

Attack Path

  1. An attacker compromises the npm package, its publisher account, or its distribution channel and publishes a malicious release under @runcomfy/cli.
  2. An operator or agent follows the documented installation command without selecting a fixed version.
  3. npm resolves the attacker-controlled release.
  4. npm i -g executes applicable lifecycle scripts and installs the package globally, or npx -y downloads and runs its CLI without requiring approval.
  5. The malicious package executes with the privileges and environment of the invoking user.
  6. It may read accessible files and environment variables, including RUNCOMFY_TOKEN, modify user-level files, or perform unauthorized network activity.

Impact Assessment

Successful exploitation could provide arbitrary code execution under the invoking user's account. The accessible s ...[truncated 353 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the CLI to an exact reviewed version, for example @runcomfy/cli@X.Y.Z, rather than resolving the latest release.
  2. Record and verify the expected package integrity hash before installation.
  3. Prefer a lockfile-backed local installation using a trusted internal or controlled registry mirror.
  4. Remove or discourage unattended npx -y execution because it automatically approves downloading and running mutable code.
  5. Review the selected package version, including lifecycle scripts, transitive dependencies, and executable entry points.
  6. Run the CLI as an unprivileged user in a sandbox or container with access limited to the required output directory and network endpoints.
  7. Supply RUNCOMFY_TOKEN only for the command that requires it and avoid exposing unrelated secrets in the process environment.
  8. Establish an update process in which new CLI versions are reviewed and their integrity values updated deliberately.
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger list contains broad, common phrases such as 'compose', 'make a song', and 'background music', which can cause the skill to activate in contexts where the user did not intend external model invocation. In this skill, unintended activation is more concerning because use of the skill can lead to authenticated API calls, token use, outbound network access, and potentially billable generation jobs.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

The skill recommends executing npx -y @runcomfy/cli without pinning an exact package version. That causes the agent or user to fetch and run whatever version is current on the registry at execution time, creating a supply-chain execution risk if the package is compromised, a malicious version is published, or a dependency is hijacked.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
96% confidence
Finding

The security section explicitly endorses npx -y @runcomfy/cli as a verified install path, but it is still an unpinned package execution flow. Even though it avoids curl-pipe installation, it still executes remote code from the package registry at runtime and inherits registry, publisher-account, and dependency compromise risks.

Content

No source excerpt is available for this finding.