Back to skill

Security audit

Audio

Security checks for vulnerabilities and agentic risk

Overview

This audio-processing skill is coherent and purpose-aligned, with some ordinary caution needed around optional cloud transcription services, API keys, and unpinned package installs.

Before installing, treat cloud transcription as third-party processing of potentially sensitive recordings, keep API tokens out of shell history and source control, and install optional Python/Conda tools in a dedicated virtual environment or container with reviewed package versions where possible.

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
transcription.md:15
Finding

Unpinned Third-Party Transcription Dependencies

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (5)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The transcript workflow instructs users to run Whisper on episode audio but gives no privacy warning about the sensitivity of spoken content or whether transcription may involve a local model versus a hosted service. In a podcast workflow, audio can contain unpublished material, personal data, guest information, or accidentally recorded private conversation, so omission of a privacy note can lead to unintentional disclosure or mishandling.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The document recommends API-based transcription services without clearly warning that audio files and their contents may be transmitted to third-party providers. In an audio-processing skill, users may reasonably assume local handling unless told otherwise, so this omission can lead to unintended disclosure of sensitive recordings or regulated data.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
90% confidence
Finding

The presence of the AssemblyAI API endpoint indicates a third-party network call as part of the workflow. While not malicious by itself, it is security-relevant because it can result in unintended transfer of sensitive audio metadata or content outside the user's environment.

Content

Scanner excerpt · transcription.md (reported line 117)May include surrounding context.

Option 3: AssemblyAI API

bash
# Upload and transcribe with speakers
curl -X POST "https://api.assemblyai.com/v2/transcript" \
  -H "authorization: YOUR_API_KEY" \
  -d '{"audio_url": "URL", "speaker_labels": true}'

External Transmission

Medium
Category
Data Exfiltration
Confidence
90% confidence
Finding

The presence of the AssemblyAI API endpoint indicates a third-party network call as part of the workflow. While not malicious by itself, it is security-relevant because it can result in unintended transfer of sensitive audio metadata or content outside the user's environment.

Content

Scanner excerpt · transcription.md (reported line 117)May include surrounding context.

Option 3: AssemblyAI API

bash
# Upload and transcribe with speakers
curl -X POST "https://api.assemblyai.com/v2/transcript" \
  -H "authorization: YOUR_API_KEY" \
  -d '{"audio_url": "URL", "speaker_labels": true}'

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

The examples show use of Hugging Face tokens and API keys but do not warn users about secure credential handling. This can encourage unsafe practices such as pasting secrets directly into shell history, scripts, shared terminals, or checked-in documentation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.