Marketing & automation systems for business
AI voice-cloning fraudprofessional firm securityAI vishingGDPR AI Actanti-fraud procedures

AI Voice-Cloning Fraud: How to Protect Your Firm

A fake WhatsApp message and an AI-cloned voice were all it took to steal tens of millions from Fideuram. Italian professional firms and SMEs are even more vulnerable — here is why, and what to do about it today.

Ovia editorial team··9 min read·Regulation and security

The Fideuram case has turned a threat many Italian professionals dismissed as science fiction into hard reality: a gang of fraudsters used an AI-cloned voice of a well-known lawyer and a fake WhatsApp message purportedly from the CEO of Intesa Sanpaolo to persuade Fideuram's then-chairman Paolo Molesini to authorise transfers of roughly €95 million. This is a real incident, dating from last February, and it has already become a landmark reference in cybersecurity circles.

If a major financial institution can fall for a scam of this kind, an accountancy practice, a law firm, a labour consultant or an Italian SME — where decision-making is often informal and authorisations still travel by phone call or chat — is at least equally exposed. The difference is that a professional firm has neither the security infrastructure nor the financial resilience of a banking group. That is precisely why the response cannot be purely technological: it must be, above all, strategic and procedural.

ⓘ Key takeaways
  • The Fideuram fraud used an AI-cloned voice and a fake WhatsApp message to move tens of millions of euros.
  • Professional firms and SMEs are ideal targets: they handle money and sensitive data through often informal, trust-based decision-making.
  • Recognising a cloned call by ear is extremely difficult — internal verification procedures matter far more than your hearing.
  • If documented protocols are missing, liability for any resulting loss can fall directly on the professional or business owner.
  • The GDPR and the EU AI Act already impose obligations on systems that process biometric voice data and on automated decision-making processes.
  • Logging authorisations in tools that produce verifiable audit trails is the most effective and provable line of defence.
In this article
  1. How an AI voice-cloning scam works
  2. Why professional firms and SMEs are ideal targets
  3. How to spot a fake AI-generated call
  4. Internal procedures to prevent AI voice fraud
  5. GDPR, AI Act and liability: what the rules say about voice fraud
  6. Tools for tracking and verifying call-based authorisations
  7. The Ovia view
  8. Frequently asked questions

How an AI voice-cloning scam works

The mechanism is simpler than it sounds. An attacker collects audio samples of the person they wish to impersonate — a few minutes of public recordings, interviews, YouTube videos or social-media clips are enough — and uses them to train a voice-synthesis model. The result is a synthetic voice capable of delivering any text with the intonation, rhythm and phonetic detail of the original. The quality achievable today makes recognition by the naked ear practically impossible for anyone.

In the Fideuram case documented by FederPrivacy, the attack combined two channels: a written WhatsApp message — easier to fake — to lower the target's guard, followed by a phone call featuring the synthetic voice of a trusted lawyer to deliver the final push towards authorising the wire transfer. This combination is now the hallmark of the most sophisticated voice fraud: a text channel prepares the ground, a voice channel closes the scam.

The technical term is *vishing* (voice phishing), but in its AI-enhanced form it represents a qualitative leap beyond the old phone calls with a foreign accent. This is no longer about exploiting inattention: it is about exploiting trust in a familiar voice.

1

Audio collectionStep 1

The attacker gathers public voice samples of the person to be cloned: interviews, videos, podcasts, voice messages.

2

Voice cloningStep 2

An AI voice-synthesis tool generates a replica of the original voice capable of delivering any text.

3

Context settingStep 3

A written message (WhatsApp, email, SMS) establishes a credible pretext and lowers the target's defences.

4

The fake callStep 4

The cloned voice calls the target and requests an urgent action: a wire transfer, a system login, a signature.

5

Execution and flightStep 5

The target complies, believing they are speaking to a trusted person. Money or data disappear before anyone notices the deception.

Why professional firms and SMEs are ideal targets

Large banks and listed groups have spent years building multi-factor authentication, escalation protocols and automatic audit trails. A five-person accountancy practice, or a thirty-employee manufacturing SME, has not. And that asymmetry is precisely what fraudsters look for.

Three characteristics make an Italian professional firm or SME particularly exposed. First: management of significant financial flows through oral, informal decision-making. The word of the owner, partner or trusted accountant carries enormous weight — an operational advantage that becomes a critical vulnerability when faced with a cloned voice. Second: access to highly sensitive third-party data — balance sheets, tax returns, payslips, court documents — making a successful breach even more valuable to an attacker. Third: deep, long-standing mutual trust between people who have known each other for years, which lowers the verification threshold further still.

As the Cybersecurity360 analysis on contemporary cyber risk highlights, today's risk does not originate inside the organisation — it spreads through trust relationships between interconnected parties. A professional firm is by definition a trust hub: the point where relationships between clients, banks, suppliers and public bodies converge. Whoever compromises it can reach all of them.

Current situation

Typical firm / SME
Wire transfer authorisations
Verbal or via chat / WhatsApp
Caller identity verification
Relies entirely on the ear
Decision log
Absent or fragmented
Written anti-fraud procedures
Rarely formalised
Team training
Occasional or non-existent

What needs to happen

Recommended approach
Wire transfer authorisations
Dual channel + tracked written confirmation
Caller identity verification
Verification code or call-back on a known number
Decision log
Tool that records who authorised what, and when
Written anti-fraud procedures
Signed, up-to-date internal protocol
Team training
At least one annual session with simulations

How to spot a fake AI-generated call

The honest answer is: often you cannot — and you should not fool yourself into thinking your ears will save you. The latest generation of synthetic voices passes perceptual tests even with trained listeners. That said, there are contextual signals that should always trigger an alarm, regardless of how authentic the voice sounds.

The first signal is artificial urgency: the request must be acted on immediately, there is no time to verify, something terrible will happen if you do not act at once. This pattern is identical in every fraud, digital or otherwise, because time is the greatest ally of anyone who wants to check and the greatest enemy of anyone who wants to deceive. The second signal is an unusual combination of channels: a request that arrives first on WhatsApp and then by phone, or vice versa, from numbers that do not match exactly with those stored in your contacts, is already an anomaly that cannot be ignored. The third signal is a request that falls outside normal procedure: if your partner has never asked you to authorise a wire transfer by phone without written confirmation, and today they do, the voice — however convincing — is not enough.

On the technical side, synthetic-voice detection tools exist, but they are still rarely deployed in the context of Italian professional firms and require integration into communications systems. The most practical and immediate defence remains procedural: deciding in advance what can and cannot be authorised verbally, before the fake call arrives.

⚠ 4 warning signs in a suspicious call
  • Artificial urgency: 'You need to do this now — there's no time to check.' Urgency is the primary pressure tool in voice fraud.
  • Request outside normal procedure: a wire transfer, a password, an access credential asked for the first time by phone from someone who usually uses other channels.
  • Caller number that does not exactly match your contacts, or a call preceded by a WhatsApp message that 'sets the scene'.
  • Inability to call back or obtain written confirmation: anyone in a hurry to leave no trace has a reason for it.

Internal procedures to prevent AI voice fraud

Effective prevention does not start with a technology tool: it starts with the decision about what can never be authorised on a verbal request alone. That decision must be made before the call arrives, written into an internal protocol, communicated to the entire team and reviewed at least once a year. This is not red tape: it is the difference between demonstrating you did everything possible and having to answer for a loss.

A minimum anti-fraud protocol for a professional firm or SME has at least three levels. The first is a list of actions that can never be authorised by voice alone: wire transfers above a defined threshold, changes to client bank details, access to management systems, sharing of credentials. The second is a dual-channel procedure: for any request on that list, confirmation must arrive via a second, independent channel — not WhatsApp on the same phone, but a corporate email or a call-back to a verified number. The third is a tracked log: every authorisation must be recorded in a system that shows who approved it, when and on what basis, so that due diligence can be demonstrated if the matter is ever challenged.

This third point also carries the most direct legal implications. If an employee executes a wire transfer on the instruction of a cloned voice, liability falls on the firm or company owner if there are no documented procedures that restricted that possibility. As Cybersecurity360's analysis on cybersecurity governance points out, the most significant regulatory violations do not stem from the absence of formal controls, but from the inability to demonstrate ongoing, informed risk management — an excellent summary of what any firm seeking to protect itself actually needs. For a deeper look at how AI affects professional liability, see our article on verifying AI output in professional firms.

Voice-fraud prevention protocol: minimum checklist for firms and SMEs

  • ✓
    Blacklist of verbal authorisationsWritten and defined: which operations can never be carried out on a phone or chat request alone.
  • ✓
    Wire transfer thresholdMaximum amount authorisable without written confirmation on an independent channel, signed by the owner.
  • ✓
    Dual-channel procedureFor every critical request: confirmation by corporate email or call-back to a verified number from your contacts.
  • ✓
    Authorisation logA tool or register that tracks who approved what, with date and time, kept securely and retrievable.
  • ✕
    Annual team trainingAt least one session per year with up-to-date examples of voice fraud and practical simulations.
  • ✕
    Protocol updateAnnual review of the protocol at a minimum, or following any incident or reported attempt.

GDPR, AI Act and liability: what the rules say about voice fraud

AI voice-cloning fraud touches the European regulatory framework on at least two fronts. The first concerns the GDPR: voice is biometric data. When an attacker clones the voice of a lawyer or an accountant to commit fraud, they are unlawfully processing a special-category personal data. But the professional's own liability does not end there: if their firm has not adopted adequate technical and organisational measures to protect its communication channels and client data, it may face challenges even as a victim of a breach, not merely as a controller.

The second front is the EU AI Act, which has been progressively entering into force across the European Union. Voice-synthesis and voice-cloning systems used to deceive natural persons fall within prohibited or high-risk AI practices, but this does not automatically protect those who fall victim to them: the professional must still have done their part in terms of preventive measures. Also relevant here is Italian Law 132/2025, which introduces specific obligations for Italian professionals who use AI tools — a regulatory context that Ovia has examined in detail in the dedicated article on Italian Law 132/2025 and client disclosure obligations.

In short: the law alone is not enough to protect you if you do not have documented procedures in place. And documented procedures are not enough if they are not backed by tools that leave a verifiable trail of every decision and authorisation. This is the point where strategy meets technology — and where a professional firm can move from being exposed to being protected.

⚠ Watch out: three mistakes that increase your legal exposure
  • Authorising wire transfers and IBAN changes by phone call or WhatsApp message alone, without written confirmation on a separate channel and without a tracked log.
  • Never having formalised a written internal anti-fraud protocol: in the event of a loss, the absence of documented procedures worsens the position of the owner or person responsible.
  • Treating the security of voice and chat channels as a 'technical' problem delegated to IT, without a strategic decision on what can and cannot be authorised verbally.

Tools for tracking and verifying call-based authorisations

The market now offers tools capable of automatically transcribing, summarising and archiving phone calls and meetings, linking each conversation to the correct client or matter. This is not only useful for productivity: it is essential for building a verifiable audit trail of every interaction — one that, if a dispute arises, demonstrates what was said, by whom and when.

A call management and transcription system integrated into the firm's daily routine turns every phone call into a searchable record: who called, when, what was decided, what actions followed. If a request for a wire transfer comes in by phone, the log exists. If it does not exist in the log, that absence is itself a detectable anomaly.

In parallel, an operational CRM with structured authorisation workflows makes it possible to define which actions require formal approval, and to record every authorisation step with date, time and user. This is not digital bureaucracy: it is about making visible and provable the due diligence that the law requires and that, in the event of fraud, can make the difference between a covered and an uncovered loss. It is the principle that Cybersecurity360 summarises as: making the invisible visible, connecting technical risk to its real business impact.

1

Transcribe every relevant callStep 1

Use an automatic transcription tool linked to your management system: every conversation becomes a record with date, time and content.

2

Link the transcript to the client and matterStep 2

The system must associate each call with the correct party, not leave it in a generic, untraceable archive.

3

Define which actions require written confirmationStep 3

In the CRM workflow, critical operations require written-channel approval before they can be executed.

4

Archive and retain the logsStep 4

Authorisation logs must be stored securely and immutably, for at least the period required by applicable regulations.

Ovia's view: procedure beats the ear every time

✦ The Ovia view: strategy and security before the tool

At Ovia we work with Italian professional firms and SMEs that manage high-value information flows and decisions every day. What we see most often is not a lack of awareness about the risk — the Fideuram case has made its mark — but a lack of a structured response: the danger is known, yet there is still no written procedure, no tracked log, no dual-channel protocol.

Our approach always starts with strategy: agreeing with the client which actions can never be authorised by voice alone, which threshold triggers an additional check, and who is responsible for what. Only then do we select the tools — call transcription, CRM with authorisation workflows, tracked archiving — that turn that strategy into something operational and provable. Security is not a product you install: it is a decision you make before the wrong call arrives.

This matters on the regulatory front too. The GDPR, the EU AI Act and Italian Law 132/2025 all require professionals to demonstrate informed, documented risk management. Saying 'I didn't know' is not enough: you need to show what you did to prevent it. Ovia's tools are designed to leave that trail — natively, without extra steps, in full compliance with Italian and European rules.

Frequently asked questions

How does an AI voice-cloning scam work?

An attacker collects public audio samples of the person they wish to impersonate and uses them to generate a synthetic voice with AI. That voice can deliver any text in a way that is nearly indistinguishable from the original. The attack typically combines a written message (WhatsApp, email) to set the scene with a phone call using the cloned voice to demand an urgent action — a wire transfer, a system login, a change of data.

Can my firm or business be hit by a voice-cloning fraud?

Yes, and the risk is higher than most people realise. Professional firms and SMEs handle money and sensitive data, and their decision-making is often informal and built on personal trust. These characteristics make them ideal targets: fraudsters look precisely for environments where an authoritative voice is enough to get something done without further checks.

How do you spot a fake call generated by artificial intelligence?

By ear alone it is very difficult: the latest synthetic voices often pass perceptual tests even with experienced listeners. The signals to watch for are contextual — artificial urgency, a request that falls outside normal procedures, a number that does not exactly match your contacts, an inability to call back or obtain written confirmation. The real defence is procedural, not perceptual.

Which internal procedures help prevent AI voice fraud?

Three fundamental levels: a written list of actions that can never be authorised on a verbal request alone (e.g. wire transfers above a set threshold, IBAN changes); a dual-channel procedure for any critical operation (confirmation by corporate email or call-back to a verified number); and a system that records every authorisation with date, time and the person responsible. Everything must be written down, communicated to the team and reviewed at least once a year.

Who is liable if an employee makes a wire transfer on the instruction of a cloned voice?

Liability tends to fall on the firm or company owner if there are no documented procedures restricting that possibility. The absence of a written protocol and a tracked authorisation log worsens the position of the person responsible in any dispute — whether in civil proceedings or before the Italian Data Protection Authority (Garante Privacy).

What does the GDPR have to do with AI voice and WhatsApp fraud?

Voice is biometric data: its unlawful cloning constitutes a GDPR violation. But the professional's own liability also extends to the measures they should have taken to protect their communication channels and their clients' data. If adequate technical and organisational measures are missing, the professional may face regulatory challenge even as a victim — not only as a data controller.

What tools can I use to verify and track call-based authorisations?

The most useful tools are automatic call-transcription systems linked to your management platform — which turn every conversation into a searchable record with date, time and content — and CRMs with structured authorisation workflows that require written confirmation before critical actions can be executed. Together they build a verifiable audit trail that demonstrates the professional's due diligence if the matter is ever challenged.

Conclusion

AI voice-cloning fraud is not a future threat: it has already happened, in Italy, targeting well-prepared and well-structured organisations. For a professional firm or an SME, the question is no longer 'can we be targeted?' but 'what have we done to limit the damage and prove it?'

The answer does not start with technology: it starts with the decision to establish, in writing, what can and cannot be authorised by phone call alone. That decision, communicated to the team and backed by tools that leave a trace, is the most concrete defence available today — and the one that Italian and European law already requires.

If you want to understand where to start for your firm or business, Ovia is available for a free initial assessment. The best time to do it is before the wrong call arrives.

An article by the Ovia editorial team, written with the support of artificial intelligence tools from the sources cited, which remain the property of their respective authors. Translated from the Italian original. This information is for general guidance and does not constitute legal or tax advice. Corrections: oviaitalia@gmail.com.

Press and hold to book

Waiting for you

Turn this article into a measurable result.

Thirty minutes on your real workflow: where the time goes, what can be safely automated and where it’s best to start.

No obligation. We work with a few clients at a time.