
BlogBusiness Voice Clone Fraud
AI Voice Cloning Is Already Inside Your Organization
Sixty-two percent of organizations have already experienced a deepfake attack, according to Gartner, and the tool behind most of them requires nothing more than a short audio clip of your CEO speaking at a conference. The average cost of a successful vishing incident is $1.5 million in incident response alone.
The call sounds exactly right: the cadence, the vocabulary, the slight hesitation before a number. Your finance team has no technical signal to flag it. AI voice cloning synthesizes a speaker's voice from recorded audio, and it now takes just 20 to 30 seconds of source material to produce a convincing replica capable of placing a real-time call to anyone inside your organization.
Spam filters, call authentication systems, and email security tools don't apply here. The attack arrives as a voice. SoSafe's security awareness research confirms that cloned voices bypass technical filters entirely, which makes organizational training and verification protocols the primary defense. Most organizations don't have one that holds up.
Four Ways This Attack Hits the Workplace
The most financially damaging variant is CEO fraud. A cloned voice of the CEO or CFO calls a finance team member directly, requests an urgent wire transfer, and asks them to keep the transaction confidential until it clears. The urgency is manufactured; the authority sounds real. In February 2024, engineering firm Arup lost $25 million when an employee joined a video call where every participant was a deepfake, including a synthetic version of a senior company officer. Voice-only attacks require even less infrastructure and are harder to detect in the moment.
IT help desk manipulation works the same way. An attacker clones the voice of a known employee, calls the help desk to request a password reset or MFA bypass, and the operator complies because the voice gives them no reason to stop. The help desk operator is doing exactly what they're trained to do.
MFA pressure attacks need no technical exploit at all. A cloned executive voice instructs an employee to approve a multi-factor authentication prompt, framing it as an IT systems test or an urgent access need. The employee approves manually, and the attacker captures the session.
Voice cloning also serves as one layer inside multi-stage phishing campaigns. An employee receives a phishing email, then gets a follow-up call from a cloned executive voice confirming the email is legitimate. Written and voice confirmation together create a false sense of legitimacy that single-channel attacks can't match.
The Procedural Gap
Most organizations have invested in email filtering, endpoint protection, and network monitoring. None of those cover a phone call. The gap is procedural: most finance or IT workflows have no standard step that requires a caller to prove their identity before a high-stakes action is taken. Voice recognition is not identity verification. What feels like confirmation is actually familiarity, and AI exploits that difference directly.
Trust Onion gives finance teams a concrete step that works even when the voice sounds exactly right. Every verified member of the organization shares access to three rotating codewords that update every 60 seconds, calculated locally on each device with no server connection required. When a call arrives claiming to be the CFO and requesting a wire transfer, a vendor payment change, or any urgent financial action, the finance team member asks one question: "What are the words?"
The real CFO knows the answer. An impersonator does not. Words rotate on a schedule, so a compromised set expires automatically within 60 seconds, leaving no window for an attacker to use them later. A Proofie™, a selfie signed using your passkey in the Trust Onion app, can add a visual layer to the same verification workflow for higher-stakes confirmations.
If a caller pressures your team to skip verification or move faster than process allows, slow down. Calling back on a known number is reasonable, but a successful callback does not prove the original caller was legitimate. Use a number sourced independently from the official directory, not one the caller provided. If you cannot complete verification through a trusted channel, do not authorize the transaction. Alert your security or compliance team immediately if you believe an impersonation attempt has occurred.
The $1.5 million incident response figure doesn't include the wire amount itself, reputational damage, or regulatory scrutiny. The cost of a verification protocol is not comparable.
A controlled voice-cloning safety demonstration
Try our tool to see just how easy voice cloning is. This controlled safety demonstration exists only to show how easy voice cloning is and to make the risk tangible. It is not a real incident or proof of anyone's identity. Your submitted sample is handled transiently to generate the fixed demonstration audio. Trust Onion does not identify you or the person from the sample. Trust Onion does not store the submitted recording, clone, or generated audio.
Public by default, under your control. Proofie™ photos and signed records are stored securely on Amazon Web Services (AWS). A Proofie™ is public by default: anyone with its link or QR code can view the photo and signed record. You can add a password to make a Proofie™ private, or delete it at any time. Deleting a Proofie™ removes its photo and signed record from our AWS storage and takes its link offline, but cannot recall copies someone has already downloaded or saved.
Frequently asked questions
How do criminals use AI voice cloning to commit CEO fraud?
Attackers clone an executive's voice from publicly available audio, then call finance teams directly to authorize wire transfers or vendor payment changes. The call sounds authentic because the voice is a convincing replica, giving employees no technical signal to flag the request as fraudulent.
Can calling back on a known number confirm a caller's identity?
Not reliably. A successful callback does not prove the original caller was legitimate. Always use a number sourced independently from a trusted company directory, not one provided by the caller, and complete a separate identity verification step before authorizing any transaction.
What is a rotating codeword protocol for voice fraud prevention?
A rotating codeword protocol assigns a set of time-based words to verified personnel. Before authorizing any high-stakes action, a team member asks the caller to provide the current words. Words rotate every 60 seconds, so a cloned voice with no access to the codewords cannot pass verification.
How common are deepfake attacks on businesses?
According to Gartner, 62% of organizations have already experienced a deepfake attack. Successful vishing incidents cost an average of $1.5 million in incident response, separate from any funds transferred during the attack.
What should a finance team member do if an executive call feels suspicious?
Ask the verification question before taking any action. If the caller cannot provide the current codewords, do not authorize the transaction. Hang up, contact your security or compliance team, and reach the executive through a number sourced independently from your company directory.
Add Trust Onion's rotating codeword check to your executive and wire-transfer approval workflows: before any wire approval, vendor change, or executive override, a finance team member asks "What are the words?" and only the real executive can answer. Protect Your Business Free.
Protect Your Business FreeCite this page
AI Voice Cloning Is Already Inside Your Organization — Trust Onion, October 11, 2026. https://trustonion.io/blog/ai-voice-cloning-workplace-fraud-enterprise



