IRM Consulting & Advisory
AI & Machine Learning Security

The Dark Side of AI

How criminals use deepfakes, voice clones and synthetic identities against SMBs and SaaS companies, with FBI, DOJ and Canadian data and a blunt table of what works versus what is theatre.

How criminals use deepfakes, cloned voices and synthetic identities to steal from businesses, and the boring controls that stop them

AI-enabled fraud is impersonation made cheap: criminals use generated video, cloned voices, fluent text and fabricated identity documents to pose as an executive, a vendor or a job candidate, then ask for a payment, a credential or system access. The trick is old. What AI changes is that a convincing fake now costs minutes, not weeks.

Every few weeks we get a version of the same call. A controller at a 70-person software company received a voice note from "the CEO" on a messaging app, followed by an email from a lookalike domain asking to change a vendor's bank details before a quarter-end payment. The voice sounded right. What stopped it was not a detection tool. It was a rule written on one page that said bank detail changes are confirmed by phone, on the number already on file, by someone other than the person who received the request.

This post is about that kind of fraud. How attackers use AI to find and exploit technical weaknesses is covered in AI-Powered Cyberattacks, and the email-side tactics are in our guide to phishing scams.

What does AI-enabled impersonation fraud look like in 2026?

Three patterns cover almost everything we see in smaller companies.

Executive and vendor impersonation. The Arup case is the reference point. According to the South China Morning Post, a finance employee received a message in January 2024 that appeared to come from the UK-based CFO about a "secret transaction." The employee joined a video conference where the CFO and other attendees were digitally recreated, then made 15 transfers to five bank accounts. Arup confirmed it was the victim in May 2024. The sequence matters: a phishing message first, then a deepfake to remove doubt.

Voice clones at scale. In May 2025 the FBI warned that since April 2025 criminals had been impersonating senior US officials with AI-generated voice messages to build rapport and take over accounts. A month later the Canadian Centre for Cyber Security and the Canadian Anti-Fraud Centre issued a joint advisory about the same tactic aimed at business executives and senior officials in Canada. If officials are being cloned, your CEO's podcast is enough training data.

Synthetic identities in hiring. The FBI's January 2025 public service announcement says North Korean IT workers have used AI and face-swapping during video interviews, then stolen source code and extorted employers with it. In June 2025 the Justice Department announced searches of 29 suspected laptop farms across 16 states and said the schemes had placed workers at more than 100 US companies. One indictment alone cited at least $3 million in damages and more than 80 stolen US identities.

How big is the problem in numbers?

The FBI's 2025 Internet Crime Report is the cleanest primary data set. It recorded 1,008,597 complaints and about $20.9 billion in reported losses. Business email compromise alone accounted for 24,768 complaints and about $3.05 billion in adjusted losses. It also breaks out AI separately: 22,364 AI-related complaints with losses above $893 million, and more than $30 million in BEC losses where AI was involved.

That last number is small next to $3 billion. Good. It tells you something useful: most money is still lost to the plain version of the scam, and AI is an accelerant, not a new category. The controls that stop a badly written fake invoice also stop a perfectly written one.

Verizon's 2026 Data Breach Investigations Report found credential abuse in 39% of breaches and third parties involved in 48%. That is where impersonation lands: a stolen login or a trusted vendor. IBM's 2026 Cost of a Data Breach study puts the global average breach at $4.99 million.

Which defenses work, and which are theatre?

This is where we disagree with much of what is being sold. Our view, from the controls we review across assessments:

Control

Verdict

Why

Call-back on a number already on file before any payment or bank detail change

Works

Defeats deepfake video, voice clones and spoofed email at once, because the attacker does not control your vendor master file

Dual approval above a set threshold, with the second approver contacted separately

Works

The Arup loss needed one person to be convinced. Two people on separate channels is a much harder target

Phishing-resistant MFA (passkeys or hardware keys) for finance, email and admin accounts

Works

Stops the account takeover that usually precedes the fake request

Identity checks at hiring: in-person or notarized ID, verified references by phone, laptop shipped only to a verified address

Works

Matches the FBI's own employer guidance on fake remote workers

A shared code word for executive requests

Partly works

Useful for small teams, but it leaks and rarely gets rotated

Deepfake-detection software on video calls

Mostly theatre

NIST reports detectors show substantial error rates on content from unfamiliar generators. It also teaches staff to trust whatever passes

Annual "spot the deepfake" training videos

Theatre

Staff cannot reliably spot good fakes. Train the procedure, not the eyeball

"Secret project" exceptions to the payment policy

Actively dangerous

Secrecy is the attacker's favorite lever. No exception should bypass a call-back

The theme is simple. Stop trying to detect the fake and verify the request instead. A detector must win every time. A call-back rule just has to be followed.

Detection is not useless. Banks verifying identity at volume get value from liveness checks. But NIST's own report on synthetic content (NIST AI 100-4) describes detection as "a constant cat-and-mouse game." For a 40-person company, a written payment procedure beats a detection subscription every time.

What this does not stop

Over-promising is how controls get ignored, so here are the limits.

  • A call-back rule does not help when the attacker has already compromised the real vendor's mailbox and phone system. You need contract-level change controls with key suppliers too.

  • Hiring checks do not catch a legitimate employee who later hands their laptop to someone else. Ongoing monitoring of logins, remote desktop tools and repository access is still needed.

  • None of this protects your brand from a deepfake of your founder posted publicly. That is a communications plan, not a security control.

  • Verification slows things down. Expect pushback in the first month.

And you probably do not need a dedicated deepfake program at all if your payments, vendor changes and hiring already run through written, verified procedures. Most companies under 200 people should spend the next dollar on the basics in the table, not on an "AI fraud" product.

What should a 30 to 200 person company do first?

The order of operations we use fits in a quarter and mostly costs time, not tools.

Days 1 to 30: lock the money

  1. Write a one-page payment and vendor change procedure: call-back on the number on file, dual approval above a threshold you choose, no exceptions for urgency or secrecy.

  2. Move finance, email and admin accounts to phishing-resistant MFA.

  3. List everyone who can send money or change bank details. It is usually more people than leadership thinks.

Days 31 to 60: lock the front door to hiring

  1. Add identity verification to remote hiring: a live ID check, reference calls to numbers you find independently, and a verified shipping address that matches the payroll record.

  2. Flag candidates whose equipment address, payroll account or contact number changes during onboarding, as the FBI recommends.

  3. Restrict new hires from installing remote desktop tools and watch for logins from unexpected locations.

Days 61 to 90: rehearse and record

  1. Run a 45-minute tabletop: a deepfake CFO call asking for an urgent transfer, and a fake IT helpdesk call asking for an MFA reset.

  2. Decide who reports what. In Canada, a loss involving personal information may trigger a breach report to the Privacy Commissioner under PIPEDA, and Quebec Law 25 requires a confidentiality incident register. In the US, report fraud to IC3 quickly and check state breach laws.

  3. Fold the results into your incident response plan.

If you want a structured starting point, our Cybersecurity Baseline Assessment checks these controls, and our process, risk and controls work turns them into written procedures your auditors will accept.

Who should own AI fraud risk in a small company?

Not IT alone. Payment fraud sits with finance, hiring fraud with HR, and someone must set policy across both. In most of our clients that person is a fractional security leader working with the CFO. A Virtual CISO engagement starts from $2,000 a month for 15 to 20 hours, compared with roughly $250,000 a year for a full-time CISO. If your team is also adopting AI tools internally, pair this with an AI governance policy so the same verification mindset covers agents and copilots.

FAQ

Can a deepfake really fool someone on a live video call?

Yes. The Arup employee joined a multi-person video conference and still made 15 transfers. A stressed employee on a short call with a senior "executive" is not hunting for artifacts.

Should we buy a deepfake-detection tool?

Not first. Detection error rates are high on new generators, according to NIST. Put the money and effort into call-back and dual-approval rules, which work regardless of how good the fake is.

How do we spot a fake remote job candidate?

Look for reused phone numbers or email addresses across applicants, reluctance to appear on camera or in person, requests to ship equipment to a different address, and changes to payment details during onboarding. Verify identity at offer and again at onboarding.

Does privacy law limit identity checks on candidates?

It shapes them. In Quebec, using biometrics such as face matching to verify identity requires the person's express consent and prior disclosure to the Commission d'accès à l'information. A document check plus a live video call is simpler and avoids that. Our data security and privacy team can help you design checks that stay within PIPEDA and US state law.

Want a second set of eyes on your payment and hiring controls? Book a consultation with IRM Consulting & Advisory.

Keep Reading

Related Articles

Our Industry Certifications

Our diverse industry experience and expertise in AI, Cybersecurity & Information Risk Management, Data Governance, Privacy and Data Protection Regulatory Compliance is endorsed by leading educational and industry certifications for the quality, value and cost-effective products and services we deliver to our clients.

Copyright © 2026 IRM Consulting & Advisory. All Rights Reserved.