Security audit

Byted Mediakit Audio

Security checks for vulnerabilities and agentic risk

Overview

The skill’s audio-processing purpose is coherent, but it needs Review because setup can expose API keys and relies on an unpinned global CLI install.

Review before installing. Use only trusted media inputs, avoid sending sensitive local files unless remote processing is intended, prefer a pinned and verified CLI version, and avoid putting API keys directly in shell commands or plaintext config files when a safer credential store is available.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (2)

T08 · Insecure Dependencies

Warning

Location: reference/shared.md:13
Finding: Unpinned Global Installation of MediaKit CLI
Content: View full analysis
Remediation: View remediation
``` - Document the expected official package publisher and npm registry. - Verify package provenance and integrity before installation, using registry signatures, checksums, or an equivalent trusted mechanism where supported. - Prefer a project-local installation with a lockfile over a global installation. - Avoid installing with administrative privileges. - Disable npm lifecycle scripts with `--ignore-scripts` when they are not required by the verified package. - Establish a controlled dependency-update process that reviews and tests new versions before changing the pinned release. ]]>

T09 · Insecure Skill Coding Practices

Warning

Location: reference/shared.md:63
Finding: API Credentials Exposed Through Command-Line Arguments and Plaintext Configuration
Content: View full analysis
--runtime --surface cli --yes mediakit-cli init --mode local-first --api-key --endpoint --output-path ~/mediakit-output --runtime --surface cli --credential-store config --yes ``` ### Technical Analysis The documented non-interactive initialization commands pass the MediaKit API key directly through the `--api-key` command-line argument. Depending on the operating system and execution environment, command-line arguments may be exposed through: - Shell history files - Process inspection utilities and process metadata - Agent execution transcripts - Terminal session recordings - Debugging or observability logs - Automation logs and error reports The second command also selects `--credential-store config`, which may persist the key in `~/.mediakit/config.json`. The instructions do not require restrictive file permissions, encryption, or an operating-system credential store. If the configuration file is readable by other users or included in backups and diagnostic archives, the credential may be disclosed. ### Attack Path 1. A user replaces `` with a valid MediaKit API token and runs one of the documented commands. 2. The complete command is recorded in shell history, an Agent transcript, terminal logging, or process metadata. 3. Alternatively, the second command stores the credential in the MediaKit configuration file without documented access-control requirements. 4. A local user, process-monitoring tool, log reader, backup reader, or other actor with access to those records obtains the token. 5. The attacker reuses the token against the configured MediaKit endpoint. 6. The attacker can perform operations permitted by the compromised credential until it is revoked or expires. ### Impact ...[truncated 515 chars]
Remediation: View remediation

SkillSpector

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 (5)

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The manifest description and the entire skill documentation are written only in Chinese, with no indication that users may interact in other languages or select a preferred locale. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The documentation instructs use of API credentials and cloud-mode media processing, but it does not clearly warn that user-provided media and related metadata may be transmitted to a remote service. In a skill with shell permission, this increases the chance that sensitive local files are uploaded or processed remotely without informed user consent, especially because cloud mode is described as a normal/default path.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 72% confidence
Finding: All user-facing instructional content in this file is presented in Chinese, with no indication that the skill is intentionally region-specific or that another language option is available. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy concern.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The documentation instructs users to probe user-supplied audio URLs over HTTP/HTTPS but does not warn that doing so causes outbound network access to third-party hosts and may disclose sensitive URLs or trigger requests to attacker-controlled infrastructure. In a shell-permitted skill that handles externally supplied URLs, this omission can lead to privacy leakage, accidental access to internal or sensitive resources if operators misuse it, and poor security decision-making by users.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 97% confidence
Finding: All natural-language instructions in the file are Chinese, and there is no indication that users may choose another language or that the skill is intentionally restricted to Chinese-speaking users. This is a language/locale policy concern under the natural-language policy rule.
Content: No source excerpt is available for this finding.