Back to skill

Security audit

Minimax Tts

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward MiniMax text-to-speech helper that sends supplied text to MiniMax and saves the returned audio locally.

Install only if you are comfortable sending the text you synthesize to MiniMax's external API. Avoid using it for secrets, regulated data, or private content unless your MiniMax account and data-handling terms are acceptable, and be careful when overriding the API URL because that would send both text and the bearer token to the chosen endpoint.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The script transmits user-provided text to a third-party MiniMax API, but it does not provide an explicit privacy warning or require user acknowledgement before sending potentially sensitive content off-host. In a skill context, users may assume text is processed locally unless clearly told otherwise, so confidential prompts, secrets, or regulated data could be disclosed unintentionally.

Vague Triggers

Medium
Confidence
90% confidence
Finding
The trigger list includes broad phrases such as 'read this aloud' and 'generate voice' that can match common user requests and cause the skill to activate unexpectedly. Because this skill sends user-provided text to an external service, unintended invocation can result in unnecessary data disclosure and surprising behavior.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill documentation describes TTS functionality but does not clearly warn users that their text will be transmitted to a third-party HTTP API. This creates a privacy and consent issue, especially if users provide sensitive, personal, or proprietary text expecting local-only processing.

Static analysis

No suspicious patterns detected.