
AI Threat Vectors Part 1: Voice Is the Next Attack Surface, and It Needs a Firewall
Voice Is the New Keyboard, and No One Is Guarding It For thirty years, “input” meant a keyboard, and security grew up around that idea: sanitise the field, validate the payload, rate-limit the endpoint. The voice broke the assumption. It now sits in call centers, banking apps, cars, wearables, and the AI agents companies ship […]
Reading Time: 10 minutes
TL:DR
- Voice is becoming the primary way people, and soon machines, give instructions to AI. Enterprises are wiring it into help desks, banking, and support agents.
- A microphone verifies a voice, not an intent. That gap is now being used for real fraud, not lab demos.
- Three seconds of public audio is enough to clone an executive to an 85% match, using free tools.
- Losses are compounding fast: from $243,000 in the first known AI voice fraud case in 2019 to $25 million in the Arup deepfake call five years later.
- Voice attacks build across a full conversation. Tone, authority, and urgency do the work. A filter that scores one utterance and moves on never sees the play develop.
- Voice agents need a guardrail that carries state across the whole session. That is the case for a stateful prompt firewall.

Voice Is the New Keyboard, and No One Is Guarding It
For thirty years, “input” meant a keyboard, and security grew up around that idea: sanitise the field, validate the payload, rate-limit the endpoint. The voice broke the assumption. It now sits in call centers, banking apps, cars, wearables, and the AI agents companies ship to talk to customers directly.
The next wave, physical AI and robotics, will take instructions almost entirely through voice, because a robot working alongside people cannot depend on a keyboard.
New AI attacks appear faster than anyone can catalog them, and the ones that work rarely look like the ones you defended against last quarter. Guessing which technique lands next is a losing game, so the only defense that holds is one that assumes the attack gets through and limits what it can do.
We bolted voice onto systems that were never designed to treat sound as a security boundary. A typed command arrives as structured text you can inspect against a schema. A spoken command arrives as a raw analog signal bundling three things at once: who is speaking, what they are saying, and what they actually intend.

From $243K to $25M: Five Years of Voice Fraud
The losses compounded a hundredfold in five years while the technical bar dropped the whole time. Same playbook, same trust exploited.
| Year | Incident | How it worked | Reported loss |
|---|---|---|---|
| 2019 | UK energy firm | Fraudsters cloned the German parent-company CEO’s voice, accent and cadence included, and called the UK chief executive to demand an urgent transfer. | $243,000 (EUR 220,000) |
| 2024 | Arup, Hong Kong | A finance employee joined a video call where the CFO and several colleagues were all deepfakes, and made 15 payments. | $25 million |
| 2023 | MGM Resorts | Attackers researched an employee on LinkedIn, phoned the IT help desk, and talked an agent into resetting credentials. | About $100 million |
Three documented voice-driven frauds. The 2019 case was called the first known case of AI voice fraud.
Deloitte’s Center for Financial Services projects that generative-AI-enabled fraud in the US will climb from $12.3 billion in 2023 to $40 billion by 2027, a 32% compound annual growth rate. Deepfake vishing is a big part of that curve, and it is aimed squarely at the workflows voice agents now run: approvals, transfers, and credential resets.

US Gen-AI fraud losses, 2023 actual and 2024 to 2027 projected at a 32% CAGR.
Source: Deloitte Center for Financial Services.
Five Attack Families Already Defeat Voice Authentication
A decade of research shows almost every layer of a voice pipeline has a working exploit. They cluster into five families.
| Attack family | What it exploits | Documented in | Does voice authentication stop it? |
|---|---|---|---|
| Deepfake and cloned voices | Systems that treat a matching voice as proof of identity | Studies of commercial assistants, McAfee cloning research | No. High-fidelity clones beat text-dependent verification, and assistants without speaker verification act on anyone. |
| Inaudible and ultrasonic injection | The gap between what a microphone registers and what a human can hear | DolphinAttack, NUIT, SurfingAttack | No. The victim hears nothing, so there is never a moment where a human could object. |
| Hidden and unintelligible commands | The difference between how a speech model and a human ear parse sound | Adversarial audio research | No. Audio that sounds like garble to a person transcribes as a clean command. |
| Third-party skill abuse | Name collisions and faked hand-offs in assistant marketplaces | Voice squatting and voice masquerading research | No. The caller is legitimate. The skill is the attacker. |
| Conversational manipulation | The system’s drive to stay consistent and helpful across a call | Every case in the timeline above | No. There is no malicious utterance to match on. Authority and urgency do the work. |
Voice-attack families and what each one defeats. Not one of them is stopped by confirming the voice at the start of a call.

Executive Voices Are Cloneable From Three Seconds of Audio
McAfee’s researchers cloned a voice to an 85% match from just three seconds of audio, and to a 95% match with a hand audio band, using tools they found free online.
Three seconds is less audio than any executive produces in one earnings call.
Earnings calls, keynotes, podcast interviews, all-hands recordings, voicemail greetings. All of it is harvestable, none of it can be recalled, and most of it was published deliberately because visibility is part of the job. The same study found that one in four adults had already encountered an AI voice scam, and 77% of those targeted lost money.
You cannot patch a CEO’s voice the way you patch a server. The only lever left is what happens on the receiving end of the call, which is why detection has to shift from “is this the real voice” to “does this request make sense given everything said so far.”

The Four-Step Anatomy of a Voice Takeover
Most voice fraud runs the same four steps. Verification happens once, in step 3. The manipulation runs across all of them.

The four-step voice takeover, with the three documented cases that used it. Three different targets, three different payloads, one identical flaw: the system trusted the voice and never questioned the intent.
Liveness Detection Loses the Cloning Arms Race
Every mainstream voice defense scores a single moment and then trusts what follows.
| Defense | What it checks | Where it breaks |
|---|---|---|
| Liveness detection | Whether this audio is a live human or a replay | Rejects a real share of genuine speech, so teams turn the sensitivity down until legitimate callers stop getting locked out. That widened gap is the attack surface. |
| Signal purification | Whether the waveform carries adversarial artefacts | Degrades real audio and fails against the strongest over-the-air attacks. |
| Speaker verification | Whether the voice matches an enrolled print | Confirms identity once, then assumes the speaker never changes and is never coerced. |
| Cumulative session scoring | Whether this request makes sense given everything said so far | Does not care whether the voice is synthetic, which is why it keeps working as cloning improves. |
Liveness detection and cloning are on the same treadmill, and the side generating the fakes moves first. Every time detection gets better at spotting synthetic artifacts, the next generation of cloning model is trained to remove exactly those artifacts. Defenders who only invest in “detect the fake” will always be one model generation behind.

How a Stateful Prompt Firewall Secures Voice Agents
This is where AccuKnox Prompt Firewall changes the model. After speech is transcribed to text, the firewall sits inline between that input and the AI, inspecting every prompt and every response against your policies before either side passes.
It carries context across the whole session instead of returning a single pass or fail, it carries context across the whole session and scores cumulative risk across turns, so it catches a request that only looks dangerous once you account for everything said before it. It links each prompt to its response as one audited interaction, applies Zero Trust decisions on every turn rather than once at the wake word, and can block, sanitize, or monitor in real time.
AccuKnox’s own research on stateful Defenses found that layering session context reduced multi-turn attack success from roughly 73% to under 9%, while keeping false positives below 0.5%. That is the exact trade a voice deployment needs: catch the slow-building fraud without locking out real customers.

The AccuKnox Prompt Firewall sits inline between your application and the model, inspecting traffic in both directions and logging every interaction.
Here are the two approaches scored against the same fraudulent call.

The same six moments of one call, scored two ways. The stateless check finishes its job before the attack starts. Risk values are illustrative of how cumulative scoring behaves.
Every transcribed turn is checked against a set of policy classes before it reaches the model, including prompt injection, PII and secrets anonymisation, toxicity, and banned topics. For a voice agent, that means a caller cannot smuggle in an injection or coax out sensitive data just because they got past the wake word.

A sample of the Prompt Firewall policy classes applied to every turn, on both the incoming
prompt and the model’s response.
A Five-Question Audit for Voice Agent Deployments
| # | Ask your team | A weak answer sounds like | Your answer |
|---|---|---|---|
| 1 | Continuity. Do we re-check identity and intent through the whole conversation, or only at the start? | “We authenticate at the top of the call.” | |
| 2 | Trajectory. Can the guardrail see authority and urgency building across turns? | “Every message is scored independently.” | |
| 3 | Cloning resilience. Does the defense assume voices can and will be cloned? | “Our voice match is 99 percent accurate.” | |
| 4 | Proof. Is every interaction logged with policy scores an auditor can read? | “We keep call recordings.” | |
| 5 | Failure mode. When the system is unsure, does it step up verification or let the request through? | “We turned sensitivity down to cut false positives.” |
The voice agent audit. If more than one row gets a weak answer, you have the same exposure that cost Arup $25 million.
Voice Is One Surface. The Same Patterns Repeat Everywhere.
The same blind spot shows up everywhere an AI system takes input it did not generate. Voice is simply the surface where the money moves first.
| Attack surface | The attack | What a stateless filter sees | AccuKnox control |
|---|---|---|---|
| Voice and transcribed input | Deepfake vishing, ultrasonic injection, help-desk social engineering | One clean utterance | Prompt Firewall, Zero Trust decision on every turn |
| Multi-turn chat | Crescendo, Deceptive Delight, many-shot jailbreaking | Five harmless messages | Prompt Firewall cumulative risk scoring, plus AI Red Teaming escalation probes |
| Ingested data and agentic tools | Indirect prompt injection, memory poisoning, tool misuse | A clean user prompt | Prompt Firewall over retrieved content, plus tool gating and audit |
| Model and dataset supply chain | Poisoned weights, unsafe or unlicensed model artifacts | Nothing. It happens upstream of the prompt | AI Model and Dataset Security |
| Shadow AI | Ungoverned model and assistant use inside the business | Nothing. The traffic never reaches your guardrail | AI-SPM discovery and posture |
The AI attack surface map used across this series. Read the third column top to bottom.
Every row says the same thing about stateless filtering.
Part 2 of this series turns to the attack that hides inside the conversation itself: multi-turn jailbreaks.
FAQs
What are voice agents attacks?
Any technique that uses voice to fool a person or an AI system, including deepfake voice cloning, vishing (voice phishing), inaudible ultrasonic commands, malicious third-party skills, and multi-turn social engineering over a call.
Can AI voice cloning really beat voice authentication?
Yes. High-fidelity cloning defeats many speaker-verification systems, and cloned voices have driven real fraud, from the first documented case in 2019 to the $25 million Arup deepfake call in 2024.
Why can’t a normal content filter stop this?
Standard filters score one prompt at a time. Voice attacks build over a full conversation, so any single utterance looks harmless. Catching them needs a guardrail that keeps state across the session.
How does AccuKnox Prompt Firewall help with voice?
Once speech is transcribed, the firewall inspects each turn inline, tracks cumulative risk across the conversation, and applies Zero Trust policy decisions per turn instead of trusting everything after the wake word. See the Prompt Firewall overview in the AccuKnox docs.
Get a LIVE Tour
Ready For A Personalized Security Assessment?
“Choosing AccuKnox was driven by opensource KubeArmor’s novel use of eBPF and LSM technologies, delivering runtime security”

Golan Ben-Oni
Chief Information Officer
“At Prudent, we advocate for a comprehensive end-to-end methodology in application and cloud security. AccuKnox excelled in all areas in our in depth evaluation.”

Manoj Kern
CIO
“Tible is committed to delivering comprehensive security, compliance, and governance for all of its stakeholders.”

Merijn Boom
Managing Director







