Audio-Layer Prompt Injection Against Claude: What's Not in the Transcript

A developer who has been building a prompt injection detection API for a few months recently shipped audio scanning and shared their findings on r/ClaudeAI. The results highlight a gap in the security of voice agents: audio-layer attacks that are invisible in logs because they bypass the text transcription pipeline.
What Works (and Doesn't) with Audio Attacks
The obvious attacks fail. Playing "ignore your previous instructions" spoken aloud into a voice input — Claude transcribes it accurately, recognizes the shape of the attack, and refuses. Same as text.
The Real Problem: Signal-Layer Attacks
The interesting cases are in the signal, not the transcript. There's a class of audio attack that embeds instructions at frequencies humans don't register as speech. The transcription comes back clean because there's nothing audible to transcribe. But depending on how the audio pipeline processes the input before transcription, signal-layer content can influence what the model receives. The attack is invisible in the logs because the logs only capture what was transcribed, not what was in the audio.
Separately, speed-shifted speech creates a different problem. Slowing audio down to 0.7x or 0.8x of normal makes it sound odd to a human listener, but transcription tools handle it accurately. Someone reading a transcript would see nothing unusual. Someone listening would notice something is slightly off but probably not why.
Implications for Voice Agents
The assumption that "check the transcript and you've checked the audio" is shakier than it looks. The text injection problem is reasonably well understood at this point, but the audio equivalent feels much less mapped. The developer has been adding audio test cases to their adversarial game at castle.bordair.io — Kingdom 4 onwards has audio levels demonstrating these attacks in practice.
Who This Matters For
Anyone building voice agent implementations using Claude or similar LLMs, especially those relying solely on transcript inspection for safety validation.
📖 Read the full source: r/ClaudeAI
👀 See Also

Critical RCE vulnerability in protobuf.js library
A critical remote code execution vulnerability in protobuf.js versions 8.0.0/7.5.4 and lower allows JavaScript code execution through malicious schemas. Patches are available in versions 8.0.1 and 7.5.5.

AI Is Breaking the Two Vulnerability Cultures: Coordinated Disclosure vs. Linux's "Bugs Are Bugs"
Jeff Kaufman analyzes how AI vulnerability discovery is fracturing both coordinated disclosure and Linux's quiet-fix culture, using the recent Copy Fail (ESP) vulnerability as a case study.

OpenClaw Patches Critical Privilege Escalation in /pair Approve Path
OpenClaw 2026.3.28 fixes a critical security vulnerability (GHSA-hc5h-pmr3-3497) where the /pair approve command allowed users with pairing privileges to approve device requests for broader scopes, including admin access. Affected versions are <= 2026.3.24.

Claude models vulnerable to invisible Unicode character hijacking, especially with tool access
Testing shows Claude Sonnet 4 is 71.2% compliant with hidden instructions embedded in invisible Unicode characters when tools are enabled, with Opus 4 reaching 100% compliance on Unicode Tags encoding. Tool access dramatically increases vulnerability across all Claude models.