Security audit

BizMuse Music Video

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent BizMuse music-video workflow that clearly discloses its external service use, credential handling, uploads, costs, and local CLI dependency.

Install only if you trust BizMuse and the npm package source. Avoid using sudo for the global install, understand that your audio, reference images, prompts, and generated media are sent to BizMuse, and manage the API key through the CLI rather than chat or project files.

A.I.G

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:5
Finding: Unpinned Global Installation of a Third-Party CLI Package
Content: View full analysis
Remediation: View remediation
``` 2. Record and verify the expected npm package integrity digest and package provenance before installation. Update the digest only after reviewing a new release. 3. Prefer a project-local installation with a committed lockfile over global installation: ```bash npm install --save-exact bizmuse-cli@ ``` Invoke the pinned local binary through a controlled wrapper or `npm exec --offline` where supported. 4. Disable npm lifecycle scripts during installation if the package does not require them: ```bash npm install --ignore-scripts --save-exact bizmuse-cli@ ``` Confirm compatibility before making this the documented installation method. 5. Run the CLI in a sandbox or restricted execution environment with access only to the media files and output directory required for the current task. 6. Avoid elevated installation. Do not run the npm command with `sudo` or an administrator account. 7. Restrict outbound network access to the endpoints required by npm during installation and BizMuse during operation. 8. Review the pinned CLI release and its dependency graph, monitor it for newly disclosed vulnerabilities, and require explicit review before upgrading. 9. Keep the existing guidance that API keys must not be entered into chat or stored in project files, and document how users can revoke or rotate a key if dependency compromise is suspected. ]]>

SkillSpector

Vulnerability Patterns

Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
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

Findings (1)

Autonomous Decision Making

Medium

Category: Excessive Agency
Confidence: 80% confidence
Finding: Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Content: Scanner excerpt · SKILL.md (reported line 56)May include surrounding context.
bizmuse auth set-api-key

text
Never ask the user to paste an API key into chat. Never print, repeat, or store credentials in project files. ## Supported Inputs

Static analysis

No suspicious patterns detected.