Back to skill

Security audit

minimax-plan-usage

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to only query MiniMax Token Plan usage, with a disclosed credential-use risk if the optional API host is misconfigured.

Install only if you are comfortable using a MiniMax Token Plan API key with this command. Keep MINIMAX_API_HOST unset or set only to an official MiniMax endpoint, and avoid running it in environments where another component could silently change that variable.

Vulnerability Patterns
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • 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)

Tainted flow: 'url' from os.environ.get (line 14, credential/environment) → requests.get (network output)

Critical
Category
Data Flow
Content
def check_usage(api_key: str) -> dict:
    url = f"{API_HOST}/v1/api/openplatform/coding_plan/remains"
    resp = requests.get(url, headers={"Authorization": f"Bearer {api_key}"}, timeout=30)
    resp.raise_for_status()
    return resp.json()
Confidence
95% confidence
Finding
The request URL is derived from the MINIMAX_API_HOST environment variable and the code sends the Bearer API key to whatever host that variable points to. In a skill/agent environment, environment variables may be influenced by deployment configuration or another component, so an attacker who can alter MINIMAX_API_HOST could redirect the request to an attacker-controlled server and capture the credential.

Static analysis

No suspicious patterns detected.