Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
iFlytek Ultra-Realistic TTS
v1.0.0iFlytek Ultra-Realistic TTS (超拟人语音合成) — synthesize natural, expressive speech from text using iFlytek's ultra-realistic voice synthesis API. Supports 50+ voi...
⭐ 0· 64·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's name/description (iFlytek Ultra-Realistic TTS) matches the code and SKILL.md: it implements a WebSocket-based TTS client for the stated endpoint. However, registry metadata lists no required environment variables while SKILL.md and scripts/tts.py clearly require XFYUN_APP_ID, XFYUN_API_KEY, and XFYUN_API_SECRET. That metadata omission is an incoherence that could mislead users into installing without realizing credentials are needed.
Instruction Scope
The runtime instructions and code scope are limited to reading text (positional arg, file, or stdin), contacting the iFlytek WebSocket endpoint, and writing an audio file — that is coherent for TTS. However, the included client disables TLS verification (ctx.check_hostname = False and ctx.verify_mode = ssl.CERT_NONE), which weakens transport security and could allow a man-in-the-middle to observe or tamper with content or credentials. The code also constructs raw WebSocket frames and performs network I/O directly; while not inherently malicious, the insecure TLS setting is a significant concern.
Install Mechanism
No install spec is provided (instruction-only with a bundled Python script). No external packages or downloads are required; the project claims to use only Python stdlib, which the script reflects. This is low install risk, but because the source/homepage is unknown, provenance is limited.
Credentials
The TTS service legitimately requires credentials (app id, api key, api secret) which the SKILL.md and script request. That by itself is proportionate to a cloud TTS client. The problem is the registry metadata incorrectly declares no required env vars — an inconsistency that may hide the need to supply sensitive credentials. Requesting three service-specific secrets is expected for this purpose, but the missing metadata and lack of a declared primary credential are problematic for safe deployment.
Persistence & Privilege
The skill does not request persistent presence (always: false) and does not modify other skills or system settings. It is user-invocable and can be invoked autonomously by the agent (default), which is normal and not a sole basis for concern.
What to consider before installing
This skill appears to implement the claimed iFlytek TTS functionality, but there are two issues you should consider before installing or using it:
1) Metadata mismatch — The registry entry claims no required environment variables, but SKILL.md and the bundled script require XFYUN_APP_ID, XFYUN_API_KEY, and XFYUN_API_SECRET. Do not provide sensitive credentials unless you trust the publisher. Ask the maintainer to fix the metadata so the required secrets are visible up front.
2) Insecure TLS — The Python WebSocket client in scripts/tts.py explicitly disables TLS certificate verification (check_hostname=False and verify_mode=ssl.CERT_NONE). This can enable man-in-the-middle attacks that could capture your API keys or audio data. Request a version that validates certificates, or run the script only in a controlled environment or over a trusted network. Prefer using an official SDK or a verified client that performs proper TLS validation.
Other suggestions:
- Verify the endpoint host and that it matches the official provider; confirm the code hasn’t been tampered with (no homepage/source is provided).
- Inspect the remainder of scripts/tts.py (file was truncated in the listing) to ensure there is no hidden data exfiltration or logging of secrets.
- Limit the API key permissions (use least privilege) and consider creating a dedicated test account/keys for evaluation.
Given these issues, treat the skill with caution. The problems look like sloppy or risky engineering rather than clear malicious intent, but they are serious enough to delay use until corrected.Like a lobster shell, security has layers — review code before you run it.
latestvk9731bpm2repa148jcg7jcqnqd83gn5j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
