My bank wants my voice as a password. Is voice ID safe against AI cloning?
Treat voice ID as a convenience, not a security control. A cloned voice has already passed a major bank's voice authentication, and the raw material for a clone is any clip of you talking, which for a podcaster is unlimited. Decline where you can, and ask for a factor you can change, like an authenticator app or a hardware key.
Cite
Global 100 Forum, "My bank wants my voice as a password. Is voice ID safe against AI cloning?", https://global100.org/forum/q/my-bank-wants-my-voice-as-a-password-is-voice-id-safe-against-ai/, accessed 2026-11-10.ok so this one is personal. my bank nags me to enrol in voice ID every time I call ("my voice is my password") and now the company I do contract audio work for wants a voice check to get into the payroll portal. two different places want my voice to be the key.
here is my problem. I have something like 400 hours of my voice on the open internet. every episode, every guest spot, clean studio audio with nothing under it. if someone wanted training material for a clone of me, I have basically published the dataset myself.
I remember the stories a couple of years back about reporters cloning their own voice to get into their accounts, but the bank says they have "liveness" and anti-spoofing now. is that real? can the system actually tell a cloned voice from a live human on a phone line, or is it mostly marketing? and is the fixed passphrase version any safer than the "just talk naturally" version?
I am not paranoid about this, I just want to know if I should say no, and what I should ask for instead. would love the security people's take.
Write something first.
Give people something to work with: at least 30 words on what happened and what you tried.
That is too long. Keep it under 6,000 characters.
Write the question as the title, 15 to 140 characters, no links.
Pick a category.
Add a name (2 to 40 characters, no links).
That email address does not look right.
That was quick. Read the thread, then try again.
The form expired. Reload the page and post again.
Something went wrong with the form. Reload and try again.
Please complete the check and post again.
Limit reached for now. Try again later.
This thread is closed to new replies.
This thread no longer accepts replies.
Something went wrong with the form. Reload and try again.
Post a reply or question first (name and email), then this browser can vote, edit and accept answers.
You cannot vote on your own post.
Only the author (within 30 days) or the forum team can do that.
That email already has an account. Use your sign-in link instead.
New accounts are paused for the moment. Try again later.
That was already posted.
8 answers
- Accepted answerTomas ReyesStaffEdits the deepfakes and provenance sections ·
Treat voice ID as a convenience, not a security control. A cloned voice has already passed a major bank's voice authentication, and the raw material for a clone is any clip of you talking, which for a podcaster is unlimited. Decline where you can, and ask for a factor you can change, like an authenticator app or a hardware key.
The demonstration most people half-remember is Joseph Cox's "How I Broke Into a Bank Account With an AI-Generated Voice" from February 2023. He recorded about five minutes of his own speech, built a clone on a free tier of a commercial voice service, and played the clips from a laptop into his phone. Lloyds Bank's Voice ID asked for his date of birth and then for the phrase "my voice is my password". It rejected the clone several times, then accepted it after he adjusted the generation settings, and he was into balances and transaction history. Lloyds said Voice ID is optional, that it sits inside a layered approach, and that it had not seen a real fraud case using synthetic voice. A social engineering specialist quoted in the piece recommended organisations move to multi-factor authentication instead. Both things can be true: the attack is rare today, and the control fails when it is tried.
On the supply side, the FTC's consumer alert "Scammers use AI to enhance their family emergency schemes" puts it plainly: all a scammer needs is a short audio clip of someone's voice, which could come from content posted online, and a cloning program. Its advice for the receiving end is "don't trust the voice". That is good advice for a bank too.
Liveness checks exist and are improving, and Hana or Sam can say more about how they fail. The practical position: the bank one is optional, so decline it. For payroll, ask HR for an app-based code or a key, and ask what they do with the voice template and for how long. The voice cloning thread covers how little audio is needed.
- Dan OkaforMember ·
My credit union describes the voiceprint as being like a fingerprint, over a hundred characteristics, unique to you. I enrolled last year and honestly it is a relief not to remember another PIN. I would assume the people building this have thought about cloning; it is their money on the line as much as ours.
Jules, your case is unusual because you have so much audio out there. For most of us there are maybe a few voicemails floating around. I would not lose sleep over it.
- Sam WhitlockMember ·
The fingerprint comparison is marketing, and it points the wrong way for a threat model. A fingerprint is hard to collect without touching you. A voice is broadcast every time you open your mouth, and in Jules's case it is literally published with show notes. Biometric security rests on the sample being hard to obtain. Voice is the one biometric you hand out for free.
Anti-spoofing is a real research area, not pure vapour. There is a whole community building countermeasures, and they do catch a lot of synthetic audio. But it is an arms race with the generators, and the defender has to win on every call while the attacker only needs one. The fixed passphrase is marginally better because the attacker needs the words too, except everyone's passphrase is the same sentence and it is printed on the bank's website.
What to ask for instead: any factor you can revoke. You cannot rotate your larynx.
- JulesMember ·
@Tomas Reyes ok that settles it. I will decline the bank one and ask payroll for an authenticator app, and I will ask Kwame's question about the data policy while I am at it. slightly horrified that five minutes of audio was enough when I have published roughly four hundred hours of myself.
- Hana SatoMember ·
Small corrections to keep the thread honest in both directions. Liveness and anti-spoofing are not marketing; they are deployed models that look for artefacts of synthesis and playback. What they are not is general. They are trained against known synthesis systems and known channels, and performance drops on a generator they have not seen or on heavily compressed phone audio. Cox's test, note, used the least sophisticated injection path possible, a laptop speaker held to a phone, and still passed after a few attempts.
On text-dependent versus free speech: the fixed phrase gives the system a direct comparison against your enrolment of the same words, which helps it a little. It also gives the attacker a fixed target. Neither variant changes the underlying problem, which is that the secret is public. The voice detector accuracy thread has the detail on why phone-line audio is the hard case.
- Dan OkaforMember ·
@Sam Whitlock fair point, and I had not thought about the collection side at all. A fingerprint takes effort to lift. My voice is on every parent voicemail I have ever left. I will go find the opt-out.
- Ingrid V.Member ·
From the platform side: we evaluated voice as a step-up factor for high-risk account actions and did not ship it. Not because it never works, but because of the failure mode. When a password leaks we force a reset and move on. When a voiceprint is defeated there is no reset. The user keeps the same voice and we have no recovery path except telling them to stop using the feature we sold them.
The second issue is retention. Enrolling means handing a biometric template to a vendor, often not the bank itself, with its own retention policy and its own breach history. Jules, that is a fair question to put to the payroll company before you enrol: who holds the template, for how long, and what happens to it when the contract ends.
- Kwame A.Member ·
One angle not yet raised: in several jurisdictions biometric identifiers have their own legal regime, and employers in particular may need informed written consent, a published retention schedule, and a stated purpose before collecting them. Illinois's Biometric Information Privacy Act is the well-known example and it explicitly covers voiceprints. I will not guess what applies where Jules lives, but "may I see your biometric data policy" is a reasonable request to make of HR before enrolling, and whether they can produce one tells you a great deal about how carefully the system was set up. Ingrid's retention question is the same point from the operational side.