Back to skill

Security audit

Audio Device Diagnostic

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward audio input diagnostic guide with a normal dependency-install caution but no evidence of hidden, destructive, or data-stealing behavior.

Install only in a normal, isolated Python environment if PyAudio is not already present, and consider pinning a reviewed PyAudio version. Non-Chinese users should review a translation before relying on the troubleshooting guidance.

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:75
Finding

Unpinned Third-Party Dependency Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 75-79
Vulnerability Type: Unpinned and mutable third-party dependency
Risk Level: Medium

Vulnerable Code

markdown
## 依赖

```bash
pip install pyaudio
text

### Technical Analysis

The documented installation command retrieves `pyaudio` without specifying a reviewed version or verifying an integrity hash. Consequently, the installed artifact may change after the skill has been audited. Package installation can also execute package-controlled build or installation logic with the privileges of the user running `pip`.

Although the audit found no evidence that the legitimate `pyaudio` package is malicious, the unpinned command creates supply-chain exposure if a future release, package-index account, distribution artifact, or configured package source is compromised. It also prevents reproducible dependency resolution.

### Attack Path

1. An attacker compromises the package publication process, a distribution artifact, or a package source configured in the user's environment.
2. The user follows the skill documentation and runs `pip install pyaudio`.
3. `pip` resolves and downloads the current mutable artifact rather than a specifically reviewed release.
4. Malicious package build or installation logic executes with the invoking user's privileges, or malicious code executes when the diagnostic script imports `pyaudio`.
5. The payload can access resources available to that user and potentially affect subsequent uses of the Python environment.

### Impact Assessment

Successful exploitation could provide arbitrary code execution with the privileges of the user performing the installation or running the diagnostic script. The affected scope may include that user's files, environment variables, application data, Python environment, and network-accessible resources. Administrative impact would require the installation to be performed from an elevated
...[truncated 258 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin pyaudio to a specifically reviewed version in a dependency file rather than installing an unconstrained latest release.
  2. Record cryptographic hashes for every accepted distribution and install with hash enforcement, for example:
    bash
    python -m pip install --require-hashes -r requirements.txt
    
  3. Populate requirements.txt with an exact version and hashes generated from trusted, reviewed artifacts.
  4. Use a trusted or organization-approved package index and disable unintended supplemental indexes to reduce dependency-confusion and source-substitution risks.
  5. Install the dependency in an isolated virtual environment under a non-administrative account.
  6. Review and update the pinned version and hashes through a controlled dependency-update process that includes vulnerability and provenance checks.
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

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The natural-language content of the skill, including the description, usage conditions, commands context, and troubleshooting guidance, is presented only in Chinese. This effectively forces a specific language for users without documenting an opt-in or stating that the skill is intended only for a Chinese-speaking context.

Content

No source excerpt is available for this finding.