Back to skill

Security audit

QQ Music

Security checks for vulnerabilities and agentic risk

Overview

The QQ Music features fit the stated purpose, but setup can automatically execute an unverified remote installer with insufficient user control.

Review and install the CLI separately before enabling this skill, using a verified release where available. Check its automatic skill installation and synchronization settings. OOMOL will mediate access to your connected QQ Music account and personal music data. The bundled instructions were fully inspected, but the remote installers and hosted connector implementation remain unverified.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied chunk performs no visible QQ Music operation. Its sole action is to fetch and execute an external installer, a materially different capability not disclosed by the description. The remote script's contents are unavailable, so its specific installation actions and other effects cannot be determined.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

The supplied chunk contains only an authentication command and implements no QQ Music search or data-reading behavior. Authentication could be a supporting implementation detail if tied to QQ Music, but the supplied code establishes no such connection.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command pipes a mutable network response directly into Bash without verifying its integrity or reviewing it; the PowerShell alternative has the same underlying problem. Compromise of the installer host or delivery pipeline could execute attacker-controlled code with the agent process's permissions, potentially exposing accessible files and credentials; HTTPS alone does not protect against a compromised source.

Content

Scanner excerpt · SKILL.md (reported line 62)May include surrounding context.

The fallback setup executes downloaded installation scripts without warning about system changes.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback directs the agent to install software by executing downloaded scripts without first explaining system changes or obtaining installation approval. Although installation supports the skill's legitimate purpose and only occurs when the CLI is missing, it expands a read-oriented request into local code execution with the agent process's permissions.

Content

No source excerpt is available for this finding.

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 83)May include surrounding context.

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources