Back to skill

Security audit

Mlx Tts

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent local text-to-speech helper, with a dependency-install supply-chain caution but no evidence of hidden or malicious behavior.

Before installing, check that you trust the mlx-audio package source and consider pinning a reviewed version instead of allowing any prerelease. The skill otherwise describes local TTS behavior with bounded output paths and no credential or remote data-exfiltration behavior in the inspected artifact.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:18
Finding

Unpinned Prerelease Dependency Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 18–21
Vulnerability Type: Unpinned third-party prerelease dependency
Risk Level: Medium

Vulnerable Code

markdown
> **注意:** 本插件依赖 `mlx-audio` Python 库。使用前请确保已安装:
> ```bash
> uv tool install mlx-audio --prerelease=allow
> ```

Technical Analysis

The documented installation command permits prerelease versions of mlx-audio without pinning the package to a specific reviewed version or verifying an integrity hash. Dependency resolution may therefore select a newer prerelease and changing transitive dependencies after the Skill has been audited.

Python package installation can process package-controlled build metadata and install executable components. Consequently, compromise of the package distribution channel, a malicious eligible release, or an unexpectedly unsafe upstream update could introduce code that runs with the permissions of the user performing the installation.

The available project contains only SKILL.md; it does not include a lockfile, hash manifest, vendored dependency, or implementation that establishes additional dependency-integrity controls.

Attack Path

  1. An attacker compromises the upstream package or publishing account, or otherwise causes a malicious prerelease to become eligible through the configured package index.
  2. A user follows the Skill's documented installation instructions.
  3. uv resolves the unpinned package and its transitive dependency graph, including prereleases.
  4. The malicious component is downloaded and installed.
  5. Package-controlled code or installed executables run with the invoking user's privileges when processed or used.

Impact Assessment

Successful exploitation could allow arbitrary code execution under the installing or invoking user's account. The resulting access may include reading user-accessible files and credentials, modifying local files, accessing network resources available to that user, or tampering ...[truncated 172 chars]

Remediation
View remediation

Remediation Suggestions

  • Replace the floating installation command with a specific, reviewed stable version, for example by using an exact == version constraint.
  • Avoid --prerelease=allow unless a particular audited prerelease is explicitly pinned and operationally necessary.
  • Commit a lockfile that fixes the complete transitive dependency graph.
  • Require package hashes or verified signatures and fail installation when integrity verification fails.
  • Use an explicitly configured trusted package index rather than relying on ambiguous or environment-dependent index configuration.
  • Test dependency updates in isolation and perform security review before changing the pinned version.
  • Run installation and TTS workloads under a dedicated, least-privileged account or sandbox with restricted filesystem and network access.
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

该 markdown 文件包含自然语言配置示例,其中 langCode 被设为 zh 作为默认值。根据规则,若技能强制特定语言且未提供用户选择或明确的区域性理由,属于语言/locale 策略风险。

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.