01The Arup case
In January 2024 an employee in the Hong Kong office of the engineering firm Arup received a message that appeared to be from the company's UK-based chief financial officer asking for a confidential transaction. They joined a video call that appeared to include the CFO and other staff, but the other participants were AI-generated. Police said the deepfakes were built from publicly available footage. The employee made 15 transfers totalling HK$200 million (about US$25.6 million) to five Hong Kong bank accounts. Arup reported it to police that month, police made the case public in February, and Arup confirmed it was the victim in May 2024. It said its internal systems were not compromised and its financial stability was not affected.
Nothing was hacked in the usual sense. The attackers did not break into a network; they impersonated authority, which is cheaper and works on people instead of software.
02Why it works
- It borrows authority. A request that appears to come from the CFO, on a video call with colleagues, in a confidential matter, is built to override the employee's own doubt.
- The raw material is public. Interviews, conference talks and social video give enough footage and audio to clone a likeness. Executives are the easiest targets because they are the most recorded.
- Controls assume identity is proven by a face. Many approval processes were written when seeing or hearing someone was proof.
- Payment rails are fast and often irreversible. Once funds leave to a mule account they are hard to claw back, and faster still if sent by instant or crypto rails, a point we return to in the ransomware economy.
03Beyond payments
The same capability scales in other directions: fake customer-support calls in a relative's cloned voice, fake job candidates, and fabricated clips during elections or a crisis. The harm to civilisation is less any single scam than the slow erosion of default trust in audio and video, which is a public good that took generations to build. When anything can be faked, everything can be denied.
04The habit that defeats it: verify out of band
- 01Treat urgency, secrecy and unusual payment instructions as the warning sign, whoever appears to be asking.
- 02Call back on a number you already hold, not one supplied in the message or on the call.
- 03Require two people to approve payments above a threshold, and for any change of beneficiary details.
- 04Agree a code word with family and key colleagues for emergency requests.
- 05Do not rely on “detecting” a deepfake by eye. Artefacts like odd blinking are disappearing; process beats perception.
The same logic applies to machine-to-machine payments. A payment instruction should be proven by something an impersonator cannot copy: a cryptographic signature, not a face. That is why signed requests and verified webhook signatures matter more as faking gets easier.
05Sources
Questions
- What was the Arup deepfake scam?
- In early 2024 a finance employee at engineering firm Arup's Hong Kong office joined a video call where the CFO and colleagues were AI-generated fakes, and made 15 transfers totalling HK$200 million (about US$25.6 million) to five bank accounts. Arup confirmed it was the victim in May 2024.
- How can you tell if a video call is a deepfake?
- You often can't, reliably. The robust defence is procedural: verify unusual requests by calling back on a number you already hold, and require two-person approval for large payments or changes of payee.
- Can crypto payments be reversed after a deepfake scam?
- Generally no: on-chain transfers are final, which is why verifying the instruction before sending matters. Card and bank payments have limited dispute and recall routes, but fast transfers are also hard to recover.
Keep reading
- How AI is making cyberattacks faster, cheaper and harder to spotAI is speeding up phishing, reconnaissance and exploitation. What CrowdStrike's 2026 report and Anthropic's disclosed AI-run espionage campaign actually show, and what is hype.
- How to verify crypto payment webhook signaturesVerify a crypto payment webhook's HMAC-SHA256 signature against the raw body, guard against replays, dedupe retries and acknowledge fast — with working Node.js code.
- How to sign crypto payment API requests (HMAC-SHA256)How to sign Payaries API requests with HMAC-SHA256, with working Node.js, Python, Go and shell code and published test vectors to check your implementation against.
- How to defend against cyberattacks: the checklist that matches how attacks actually happenA short, evidence-based defence checklist for a business or shop: exposure, patching, MFA, backups, verification, supplier risk and payment controls, drawn from real 2024–2026 incidents.
- What is cryptocurrency? A plain-English guideWhat cryptocurrency is, how it differs from bank money, how wallets and keys work, the main types (Bitcoin, Ethereum, stablecoins) and how businesses accept it.