Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

MiniMax Multimodal (Speech + Image)

v1.0.1

MiniMax 多模态技能 — 接入 MiniMax Token Plan 接口,语音合成(TTS/音色克隆/音色设计) 和图片生成(文生图/图生图)。使用 speech-2.8-hd(语音)和 image-01(图像)模型, 消费 Token Plan 额度。当用户提到语音合成、音色克隆、图片生成、文生图、图生...

1· 64·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The scripts implement text-to-speech, voice cloning, voice design, image generation and image editing matching the SKILL.md description — network calls go only to the stated MiniMax API base URLs. However, the registry metadata lists no required environment variables while the SKILL.md and the code both require MINIMAX_API_KEY (and optionally MINIMAX_REGION). That metadata omission is inconsistent and should be corrected.
Instruction Scope
Runtime instructions and code stay within the stated purpose (calling remote APIs and saving returned media). Important operational behavior: voice cloning will upload local audio files to the remote /files endpoint, and image generation may download URLs returned by the API. These actions transmit user data to the provider and can consume Token Plan credits — the instructions do not ask the agent to read unrelated system files or other credentials.
!
Install Mechanism
This is an instruction-only skill with bundled Python scripts and no install spec. The scripts import the 'requests' library but the skill does not declare that dependency or provide an install step; that mismatch may lead to runtime failures or hidden additional setup. No external download URLs are used by the installer, which is lower risk, but the missing dependency declaration is an omission.
!
Credentials
The code legitimately requires MINIMAX_API_KEY (and optionally MINIMAX_REGION), and the SKILL.md documents these. However, the skill registry metadata lists no required env vars/primary credential. The requested environment access (an API key that can consume billing credits) is proportionate to the feature set, but the metadata mismatch is a packaging/visibility problem that could cause accidental exposures or misuse of credentials.
Persistence & Privilege
The skill does not request 'always: true' and does not modify other skills or system settings. It does not persist credentials itself; it reads MINIMAX_API_KEY from environment as expected. Autonomous invocation is allowed (platform default) but not combined with other high-risk indicators here.
What to consider before installing
Before installing, consider the following: - Verify the provider domains (https://api.minimaxi.com and https://api.minimax.io) are the legitimate MiniMax endpoints you expect. If unsure, contact the provider or check an authoritative homepage — the skill lists no homepage. - Treat MINIMAX_API_KEY as sensitive: the client will send it with every request and the service will charge Token Plan credits for usage (TTS, cloning, image generation). Ensure you understand billing and rate limits. - Voice cloning uploads local audio to the remote /files endpoint. Do not upload private or sensitive audio without explicit consent — this transmits user data to the provider. - The skill bundles Python scripts that import the 'requests' library but does not declare dependencies or provide an install step. Install 'requests' in your environment or run in an isolated/sandboxed environment first. - The registry metadata omits the required env vars (MINIMAX_API_KEY, MINIMAX_REGION). This is a packaging inconsistency; ask the publisher to update metadata so automated policy/permission checks can surface required credentials before installation. - The image client will download URLs returned by the API. While expected, this means the skill may fetch remote content; consider network restrictions if you run in a sensitive environment. - If you plan to use this in production or with sensitive data, request additional provenance (publisher identity, homepage, or source repo) and run the code in a controlled test environment first. If you cannot verify the provider or correct the metadata/dependency omissions, treat the skill as higher risk and avoid providing production credentials or sensitive data.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fmej5hjssd680nyh1m5rbc583mhyr

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments