Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 084
No. 084 Critical Brief · Regulatory Attribute Proof

Hong Kong deepfake meeting fraud (Arup): trusting a pre-recorded video call that faked the UK CFO and colleagues, a finance employee sent about HK$200 million in 15 transfers (Hong Kong government LegCo reply, Arup confirmation)

≈ HK$200million
Sent (about US$25.6 million), on instructions in the name of the UK head-office CFO
15transfers
Made within one week, to five Hong Kong bank accounts
01-29→05-16
From the police report to Arup confirming it was the victim
CountryHong Kong / UK
Incident date2024-01-29
Published2026-06-26
Revised v2.1 · 2026-11-02
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

The employee suspected the first message of being phishing, but a call full of familiar faces and voices dispelled the doubt. The call was a recording with no dialogue, the fake CFO ended it on a pretext, and further instructions came by messaging app and similar channels. The employee checked with the UK head office and realised it was a fraud only after the transfers had gone through. A meeting of familiar faces and voices does not, by itself, show that a payment instruction is genuine.

Exhibit 1Detection vs pre-execution check

A pre-execution check means confirming with the person, on another channel and before a payment goes out, that the instruction is genuine, and keeping a record. Detection means noticing after the fraud comes to light. The dates below are when the police and Arup confirmed or disclosed each point, not when the transfers were made.

Pre-execution check · not known from the disclosuresBefore paying, check on a separate channel, through a registered contact
What was confirmedAbout HK$200M sent in 15 transfers
Head office was checked only afterwards
Detection · noticedThe employee checks with head office and the fraud is found
2024-01 (mid)
Doubt dispelled by the call
01-29
Reported to police
02-02
Police disclose the case
05-16
Arup confirms it was the victim

What got through

What got through
Transfers by a finance employee to outside bank accounts, on instructions in the name of the UK head-office CFO. They went to five Hong Kong accounts, split across one week (Hong Kong government LegCo reply).
What was stopped
The employee suspected the first message of being phishing. In the end the employee checked with head office and noticed the fraud, but after the transfers.
What reached the receiving side
In general, faces seen and voices heard on a video call reach a payment process as a sign that the person giving the instruction approved it. Whether the video and voices are genuine cannot be told from the meeting screen.
Not disclosed
The date of the video call, and how many people appeared in it (reports differ). As of October 2026, no arrests or recovery of funds in this case have been reported.

Pre-execution check

Whatever the route, the condition for telling them apart is that whoever executes a payment checks, before it goes out, that the instruction is genuine, on a channel other than the one it came in on, through a contact registered in advance.

The core of this case
A meeting of familiar faces and voices does not, by itself, show that a payment instruction is genuine.
Who approves
The person the instruction claims to come from (a manager or head office). The approval is obtained by calling back a phone number or account registered in advance, such as the internal directory. Contacts given in the instruction, or checks inside the same meeting or chat, do not count.
Where it is checked
The process that executes the payment. Transfers that meet set conditions, such as amount or a new payee, are held and not made until they match the person’s approval. Treat “secret” and “urgent” as reasons to hold.
What is recorded
For each transfer, who confirmed it, through which channel and when, kept apart from the payment process in a form that can be shown to a third party later.

“The CFO appeared on the call” and “the CFO ordered this payment” are separate facts. A case where a made-up video was used to get past an identity check is the eKYC liveness bypass.

What Lemma does

Lemma builds the pre-execution check into the side that executes payments. It does not look for intrusions; it checks, before a payment goes out, that the instruction rests on the person’s approval, through a registered contact.

Industries and operations to watch

IndustryFinance & accounting
Finance and accounting teams that may be told to pay by an overseas head office or parent. The more an executive’s video and voice are public from talks and social media, the more raw material exists for a fake.
OperationApproval & sign-off
Paying on the strength of a manager’s instruction or approval. Here, seeming to meet the person who gave the instruction on a call stood in for approval.

Current controls vs Lemma

The route in this case is a pre-recorded video call plus follow-up instructions by messaging app and email. Other routes (such as the registered contact itself being taken over) have not been disclosed, so they are not split into columns and are covered in the note.

Control Payment instruction delivered by a video call and follow-up messages (this case)
Caution about suspicious messages Partial
Confirming with a manager on a video call Ineffective
Approval by more than one person Partial
Checking with head office Partial
Lemma (pre-execution check) Effective

Caution about suspicious messages: the employee doubted the first message, but the following meeting dispelled the doubt. Confirming with a manager on a video call: the meeting used to confirm was itself fake video and voices. Approval by more than one person still passes if approvers rely on the same meeting or the same channel’s instructions. Checking with head office revealed the fraud, but only after the transfers. Lemma checks the person’s approval, through a registered contact on a channel other than the meeting, before the payment.

Note: Lemma’s check works only when it is built into the process that executes payments and the contact used for approval is managed apart from the meeting and messages that carry the instruction. If the registered contact itself is hijacked, a separate-channel check passes too. The extra step also delays urgent legitimate payments. The police’s spotting tips (asking the person to move, testing with conversation) work against recorded fakes, but video generation keeps improving, so spotting alone cannot be relied on. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.

CheckChecklist

Three things to confirm in your organisation about payment instructions from managers or head office

  • Is there a set procedure to confirm a payment instruction in a manager’s name with them through a separate channel?
  • Is that check impossible to skip, whatever the amount or a “secret” label?
  • When an employee doubts an instruction, is it clear who they can stop and consult?

Facts and timeline

Who
A finance employee at the Hong Kong office of Arup, a major UK engineering firm. The instructions came in the name of the UK head-office CFO.
Loss
About HK$200 million (about US$25.6 million), sent in 15 transfers to five Hong Kong bank accounts within one week.
How
In mid-January a message in the CFO’s name proposed a “secret transaction”. The employee was suspicious, but the CFO and colleagues appeared on a video call the employee was invited to, and all of them were fakes. Police said it was a recording made from video and audio posted on YouTube and elsewhere, with no dialogue with the employee. The fake CFO ended the meeting on a pretext and continued the instructions by messaging app, email and one-to-one video calls.
Discovery
The employee checked with the UK head office. The case was reported to police on January 29.
Internal systems
Arup said none of its internal systems were compromised and its finances and operations were not affected. Its CIO later called it “technology-enhanced social engineering”.
Investigation
Still under investigation as of June 2024 (LegCo reply). As of October 2026, no arrests or recovery of funds in this case have been reported.

Glossary
Deepfake — AI-made video or audio that imitates a real person. Publicly posted video and audio are the raw material.
Business email compromise (BEC) — Fraud that poses as an executive or supplier to order a payment or a change of bank details. Here a video call was added to the email.
Callback — Calling the person back on a contact registered in advance, not the one the instruction came from, to confirm it is really them.

Timeline

2024-01 (mid)
A message in the name of the UK head-office CFO reaches the employee. It is about a secret transaction, and the employee suspects phishing.
The following week
The employee joins the video call and, following instructions, makes 15 transfers to five accounts.
2024-01-29
After checking with head office, the employee realises it is a fraud and the case is reported to police.
2024-02-02
Hong Kong police’s Cyber Security and Technology Crime Bureau (CSTCB) discloses the case at a briefing, without naming the company.
2024-05-16
Arup confirms to CNN and others that it was the victim: “fake voices and images were used”.
2024-06-26
Hong Kong’s Secretary for Security answers in the Legislative Council: the meeting was pre-recorded with no interaction, and the case is under investigation.

Facts rest on the Hong Kong government’s Legislative Council reply (primary), Arup’s statement and its CIO’s interview, and reporting of the police briefing. The date of the video call has not been disclosed, and reports differ on how many people appeared in it. What has not been disclosed does not mean there were no controls.

After disclosure

  • Hong Kong police: Advised testing a suspicious video call by asking the person to move their head or by probing with questions, and calling to check when a relative or friend asks for money (LegCo reply).
  • Arup: Said attacks such as invoice fraud, phishing, WhatsApp voice spoofing and deepfakes were rising in number and sophistication.

Sources

  1. Primary, LegCo replyHong Kong SAR Government, Security Bureau “LCQ9: Combating frauds involving deepfake”2024-06-26 · info.gov.hk/gia/general/202406/26/P2024062600192
  2. Primary, Arup CIO interviewWorld Economic Forum “‘This happens more frequently than people realize’: Arup chief on the lessons learned from a $25m deepfake crime”2025-02-04 · weforum.org/stories/2025/02/deepfake-ai-cybercrime-arup
6 more (reporting, analysis)
  1. Reporting, quotes Arup’s statementCNN “Arup revealed as victim of $25 million deepfake scam involving Hong Kong employee”2024-05-16 · edition.cnn.com/2024/…
  2. Reporting, quotes Arup’s statementFortune “A deepfake ‘CFO’ tricked the British design firm behind the Sydney Opera House in $25 million fraud”2024-05-17 · fortune.com/europe/…
  3. Reporting, police briefingThe Standard “HK’s first deepfake video conference scam involving HK$200 million”2024-02-04 · thestandard.com.hk/news/…
  4. Reporting, AFPHong Kong Free Press “Multinational loses HK$200 million to deepfake video scam”2024-02-05 · hongkongfp.com/2024/…
  5. ReportingCNN “Finance worker pays out $25 million after video call with deepfake ‘chief financial officer’”2024-02-04 · edition.cnn.com/2024/…
  6. ReportingSouth China Morning Post “‘Everyone looked real’: multinational firm’s Hong Kong office loses HK$200 million after scammers stage deepfake video meeting”2024-02-04 · scmp.com/news/…

References: “The last layer left for cyber defense in the age of AI”, “Proof-as-Auth: sign in without ever sending your key”

The same method elsewhereSee all 16 "Payee & bank-account changes" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"Hong Kong deepfake meeting fraud (Arup): trusting a pre-recorded video call that faked the UK CFO and colleagues, a finance employee sent about HK$200 million in 15 transfers (Hong Kong government LegCo reply, Arup confirmation)".
Lemma Critical Brief No.084. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/084-hong-kong-deepfake-video-call-fraud/
Read nextNext
All Briefs →
Revision History

Current version: 2.1

Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.