Coder Legion - Recent posts tagged deepfake

The Deepfake That Signed Off on $25 Million: A Teardown of the Arup CFO Video-Call Heist (Feb 2024)

Thu, 29 Oct 2026 07:45:39 +0000

Originally published at vibeagentmaking.com.

In January 2024 an Arup employee in Hong Kong made 15 transfers totalling HK$200 million after a video call on which every other participant was a pre-recorded deepfake. The rules of wire transfers decided in 1989 that recognizing a signature is not by itself a security procedure, and the one check that exposed the fraud came after the money had moved.

In January 2024, an employee in the finance department of Arup's Hong Kong office joined a video conference. The engineering firm's chief financial officer, who works from the United Kingdom, appeared on the call, and so did other colleagues the employee recognized. Over the following week the employee made 15 transfers totalling HK$200 million, about US$25.6 million, to five bank accounts.

"(In the) multi-person video conference, it turns out that everyone [he saw] was fake," Acting Senior Superintendent Baron Chan Shun-ching of the Hong Kong police told the public broadcaster RTHK when the force described the case. Every face and every voice on the call was synthetic except the victim's own.

The date in the headline is when the world heard about it. The money moved in January. The police made the case public at a briefing on Friday, February 2, without naming the company, and Arup confirmed it was the victim on May 17, after the Financial Times reported it. Arup is a large and sophisticated firm, with 18,500 employees in 34 offices, and it worked on the Sydney Opera House and designed Beijing's Bird's Nest stadium. That is part of why the case is worth taking apart slowly.

The artifact, in order

The public record for this incident is thin, and nearly all of it comes from two places: the Hong Kong police, who described the case in February 2024, and Arup, which confirmed it in May 2024 and talked about it in 2025. Read in order, their accounts give a sequence of five steps.

First, a message. In mid-January the employee received what the South China Morning Post, citing police, called "a phishing message ... that appeared to be from the company's CFO based in the United Kingdom saying a secret transaction had to be carried out." The employee's first read of it was correct. According to Chan, the worker initially "suspected it was a phishing email, as it talked of the need for a secret transaction to be carried out."

Second, the meeting. The fraudsters answered that doubt with a video conference. Police told AFP that the employee received "video conference calls from someone posing as senior officers of the company requesting to transfer money to designated bank accounts." Chan said the call had several participants and that all of them except the victim were impersonated, and he said where the material came from: "Scammers found publicly available video and audio of the impersonation targets via YouTube, then used deepfake technology to emulate their voices." Then he added the detail that most later retellings drop. As AFP reported it, "the deepfake videos were pre-recorded and did not involve dialogue or interaction with the victim." The meeting was a playback. Nobody on it had to answer a question.

It worked anyway. Chan said the worker "put aside his early doubts after the video call because other people in attendance had looked and sounded just like colleagues he recognized." That sentence is the whole attack. A person's judgment had caught the phishing message. The meeting existed to overrule that judgment, and it did.

Third, the payments: "15 transfers totalling HK$200 million to five bank accounts over a week in January," as the Post summarized the police account in May.

Fourth, the discovery. CNN's February report gives it one line: "The scam involving the fake CFO was only discovered when the employee later checked with the corporation's head office." Police received the report on January 29, AFP said, "at which point some HK$200 million (US$26 million) had already been lost via 15 transfers."

Fifth, what was not touched. Arup's statement in May: "Our financial stability and business operations were not affected and none of our internal systems were compromised." Its global chief information officer, Rob Greig, later called the incident "technology-enhanced social engineering" and said: "It wasn't even a cyberattack in the purest sense. None of our systems were compromised and there was no data affected."

What the record does not say

None of these sources says anything about Arup's payment controls. It does not say who else, if anyone, approved the 15 transfers, what limits applied, whether payments to new accounts were held, or whether a callback rule existed and was skipped. Arup's spokesperson told CNN in May that the company could not "go into details at this stage as the incident is still the subject of an ongoing investigation." When police briefed AFP in February they said "no arrest has been made so far," and I found no later report of an arrest or of the money being recovered.

The retellings have filled the gap anyway. The AI Incident Database notes in its entry that the case "has become a recurring reference for reports on AI-powered scams," and that "its emergence as a shorthand in journalism is worthy of note in and of itself." Shorthand collects detail as it travels. A 2026 VentureBeat retrospective puts the call on Zoom, says the first wire transfer "took minutes," and states that there was "No second approver, no out-of-band confirmation, no system-enforced hold." None of those details appears in the police statements or in Arup's. The database's editors observe that it is cited "particularly when discussing the dangers of deepfake technology in real-time video conferencing," while the police described clips that were recorded in advance.

So a teardown has to work the way an engineer works an incident that left no logs: from the outcome back to the controls that would have stopped it, saying at each step which part is inference.

A rule written in 1989

Money movement stopped trusting recognition a long time ago, and the rule is written down. Article 4A of the Uniform Commercial Code, the American law of wire transfers, was approved in 1989. Its definition of a "security procedure" lists what can count as one: "algorithms or other codes, identifying words or numbers, encryption, callback procedures, or similar security devices." Then it adds a sentence that reads, thirty-five years on, as if it were written about Arup: "Comparison of a signature on a payment order or communication with an authorized specimen signature of the customer is not by itself a security procedure."

A signature check is recognition. You hold the thing in front of you against what you know the real one looks like. The drafters did not call that useless. They said it could not stand alone, and the reason is not hard to see: a good enough forgery passes a comparison by definition. A face on a video call is a signature that moves.

Article 4A is American law and did not govern transfers out of Hong Kong. I cite it for what the people who wrote the rules of wire transfers decided about recognition, and the same thinking runs through the checklists bank examiners work from. The examiner's guide of the National Credit Union Administration, the US regulator for credit unions, tells examiners to "ensure credit union controls address adequate separation of duties between initiators, approvers, and reconcilers," to check funds-transfer agreements for "telephone call-back requirements," and to look for "dual-control verification." The first of the FBI's prevention tips for business email compromise is one line: "Use secondary channels and/or two-factor authentication to verify requests for changes in account information."

That family is not small. The FBI's Internet Crime Complaint Center counted 305,033 business email compromise incidents, domestic and international, between October 2013 and December 2023, with $55,499,915,582 in exposed losses. In its 2023 data, "international banks located in the United Kingdom and Hong Kong often acted as an intermediary stop for funds." The Arup case is the video-call version of a fraud the payments world has been fighting for a decade, in one of the places where that fraud's money habitually passes through.

What these controls share is that they do not care how convincing the request was. A callback goes to a number the firm already had on file, so it reaches the real chief financial officer however good the fake one looked. A second approver who has to confirm through a separate channel adds a person the fraudsters must also fool, on a line they do not control. The control's strength does not depend on the attack's weakness. That is the design principle, and it is why the quality of the deepfake, which is where most of the coverage looked, is the least important variable in the case.

The gates, reverse-engineered

With that template, the outcome narrows down which gates were missing or ineffective, even though the record never names them. What follows is inference, and I will say where.

An out-of-band confirmation before the first transfer. This is the gate we can be surest about, because the case contains its test. When the employee checked with head office, the fraud collapsed on contact. The confirmation that would have stopped all 15 transfers did take place. It took place after them. Either no rule required that check before money moved, or the rule could be satisfied through a channel the fraudsters controlled, such as a reply to their own message or another call they set up. The record does not say which.

An independent second approver. The record does not say whether anyone else signed off. If someone did, they signed off on the same evidence, the call, which means the second approval was not independent. What makes dual control work is the second channel as much as the second person. Two people who watched the same video are one control.

A hold on new payees and a limit on velocity. Five accounts received 15 transfers in about a week. The examiner's guide tells examiners to review "typical daily transaction volume," because "unusual transaction amounts or volumes may reflect fraudulent/erroneous activity or weak controls." Whether Arup's systems had holds or limits of that kind, and what they were set to, is not public.

And the one gate that clearly did fire was the human one. The employee spotted the first message as phishing. Everything after that was the attackers' answer to a control that worked.

Why the fake was cheap

The attackers did not need anything Arup protected. Chan said they built the participants from "publicly available video and audio of the impersonation targets via YouTube." A firm whose leaders speak at conferences and appear in the media has, without meaning to, published the training data for its own impersonation. The more visible its people are, the cheaper they are to copy, and that exposure grows with the communications budget, not the IT budget.

Nor did they need the newest technology. Pre-recorded clips were enough. Greig, interviewed by the World Economic Forum a year later, put it plainly: "It's freely available to someone with very little technical skill to copy a voice, image or even a video." Then he tried the harder version himself. "After the incident, I was curious so I attempted to make a deepfake video of myself in real time. It took me, with some open source software, about 45 minutes." He was candid about the result: "It wasn't particularly convincing." The attack on his firm never had to be convincing in real time. It only had to hold up through a meeting in which nobody asked it anything.

Recognition by machine had fared no better. At the same February briefing, police described a separate scheme from the previous July to September, in which eight stolen identity cards had been used for 90 loan applications and 54 bank account registrations, and in which, on at least 20 occasions, "AI deepfakes had been used to trick facial recognition programs by imitating the people pictured on the identity cards." Human eyes and automated face matching fell to the same trick in the same city, a few months apart.

Move the last line to the top

The February account turns on one late moment: the employee checks with head office, and the fraud falls apart. That check is the control. It costs almost nothing and depends on nobody's eyes, and when it was finally used it worked at once. In the Arup sequence it came last, once the message had been read, the meeting held and all 15 transfers made.

The practical version is short enough to fit on a card. Wherever a person can approve an irreversible action because they recognize who is asking, by face, by voice or by writing style, put a confirmation in front of it that runs through a channel set up before the request arrived. A number already on file will do. So will a second approver who must reach the requester independently, or a code agreed in advance. Then have the system enforce the order, so the check comes before the money moves. None of this requires detecting the deepfake. It is built so that it never has to.

In the sentence of CNN's February report that describes the fraud being caught, the word to change is "later."

Sources:

Heather Chen and Kathleen Magramo, "Finance worker pays out $25 million after video call with deepfake 'chief financial officer'," CNN, February 4, 2024. https://www.cnn.com/2024/02/04/asia/deepfake-cfo-scam-hong-kong-intl-hnk/index.html
AFP, "Multinational loses HK$200 million to deepfake video conference scam, Hong Kong police say," Hong Kong Free Press, February 5, 2024. https://hongkongfp.com/2024/02/05/multinational-loses-hk200-million-to-deepfake-video-conference-scam-hong-kong-police-say/
Harvey Kong, "'Everyone looked real': multinational firm's Hong Kong office loses HK$200 million after scammers stage deepfake video meeting," South China Morning Post, February 4, 2024. https://www.scmp.com/news/hong-kong/law-and-crime/article/3250851/everyone-looked-real-multinational-firms-hong-kong-office-loses-hk200-million-after-scammers-stage
Lo Hoi-ying, "UK multinational Arup confirmed as victim of HK$200 million deepfake scam that used digital version of CFO to dupe Hong Kong employee," South China Morning Post, May 17, 2024. https://www.scmp.com/news/hong-kong/law-and-crime/article/3263151/uk-multinational-arup-confirmed-victim-hk200-million-deepfake-scam-used-digital-version-cfo-dupe
Kathleen Magramo, "British engineering giant Arup revealed as $25 million deepfake scam victim," CNN, May 17, 2024. https://www.cnn.com/2024/05/16/tech/arup-deepfake-scam-loss-hong-kong-intl-hnk
"Arup victim of multimillion-dollar deepfake video scam in Hong Kong," Dezeen, May 17, 2024. https://www.dezeen.com/2024/05/17/arup-victim-deepfake-video-scam/
"'This happens more frequently than people realize': Arup chief on the lessons learned from a $25m deepfake crime," interview with Rob Greig, World Economic Forum, February 4, 2025. https://www.weforum.org/stories/2025/02/deepfake-ai-cybercrime-arup/
Uniform Commercial Code § 4A-201, "Security Procedure," as published by the Legal Information Institute, Cornell Law School, and in the Federal Reserve's Regulation J materials. https://www.law.cornell.edu/ucc/4A/4A-201 and https://www.federalreserve.gov/frrs/regulations/uniform-commercial-code-article-4a-funds-transfers.htm
Uniform Law Commission, "UCC Article 4A, Funds Transfers (1989)." https://www.uniformlaws.org/viewdocument/enactment-kit-54?CommunityKey=2985cf6d-9c22-4abe-abf1-1f36f8a27201&tab=librarydocuments
National Credit Union Administration, Examiner's Guide, "Wire Transfer Review Procedures." https://publishedguides.ncua.gov/examiner/Content/ExaminersGuide/ElectronicPaymentSystems/ExamProcedures/WireTransfer2-Review.htm
FBI Internet Crime Complaint Center, PSA I-091124-PSA, "Business Email Compromise: The $55 Billion Scam," September 11, 2024, "Statistical Data" and the prevention tips. https://www.ic3.gov/PSA/2024/PSA240911
AI Incident Database, Incident 634, editor's note. https://incidentdatabase.ai/cite/634/
Louis Columbus, "The $25.6 million deepfake that human review, MFA and liveness detection all missed," VentureBeat, May 21, 2026, cited here for how the case has been retold. https://venturebeat.com/security/25-million-deepfake-that-human-review-mfa-and-liveness-detection-all-missed

Confirm through a channel the request did not arrive on.

The control that would have stopped this fraud did not have to detect the deepfake. It only had to happen before

    the money moved, through a channel set up in advance. The same rule applies when software agents can initiate
    payments or other actions that cannot be undone: the order of request, confirmation and execution should be
    enforced, and afterwards it should be checkable. Chain of Consciousness keeps a tamper-evident record of an
    agent's actions, so that order can be verified later by someone who was not there.

pip install chain-of-consciousness
npm install chain-of-consciousness

Or start without installing anything: Hosted Chain of Consciousness.

The Deepfake War Just Got Real-Time.

Tue, 16 Jun 2026 23:04:47 +0000

The Real-Time Deepfake Defense: Architecting Digital Trust

Introduction

The digital landscape has been irrevocably altered by deepfakes – synthetic media so convincing they blur the lines between reality and fabrication. From misinforming the public to impersonating individuals, the threat has escalated rapidly, challenging our fundamental trust in online content. For years, the approach to identifying deepfakes has largely been retrospective: analysis after a video has gone viral, a laborious and often too-late process. But the deepfake war is finally shifting gears. We are now witnessing critical breakthroughs in real-time deepfake detection, moving beyond post-factum analysis to a proactive defense. This tutorial outlines the architectural concepts behind these emergent platforms, detailing how multi-modal AI and cryptographic provenance are converging to build the digital trust infrastructure of tomorrow, fighting back against deception as it unfolds.

While the specific implementations of these cutting-edge platforms remain proprietary, the underlying principles and components can be conceptualized into a robust real-time detection system. This “code layout” focuses on the workflow and interdependencies of critical modules designed for high-throughput, low-latency processing.

System Overview: RealTimeDeepfakeDefender

class RealTimeDeepfakeDefender:
    def __init__(self):
        self.stream_ingestion_module = StreamIngestionModule()
        self.multi_modal_analysis_engine = MultiModalAnalysisEngine()
        self.provenance_validator = CryptographicProvenanceValidator()
        self.fusion_decision_engine = FusionAndDecisionEngine()
        self.alert_system = RealTimeAlertSystem()

    def process_stream(self, data_chunk):
        # 1. Ingest streaming data (video, audio, metadata)
        raw_stream_data = self.stream_ingestion_module.ingest(data_chunk)

        # 2. Asynchronously analyze multiple modalities
        #    (Running in parallel for speed)
        img_analysis_result = self.multi_modal_analysis_engine.analyze_image(raw_stream_data.video_frame)
        aud_analysis_result = self.multi_modal_analysis_engine.analyze_audio(raw_stream_data.audio_segment)
        phy_analysis_result = self.multi_modal_analysis_engine.analyze_physiological_cues(raw_stream_data.video_frame)

        # 3. Simultaneously validate cryptographic provenance
        provenance_status = self.provenance_validator.validate_c2pa_metadata(raw_stream_data.metadata)

        # 4. Fuse results and make real-time decision
        detection_score, confidence = self.fusion_decision_engine.aggregate_and_score(
            img_analysis_result,
            aud_analysis_result,
            phy_analysis_result,
            provenance_status
        )

        # 5. Take action if deepfake detected
        if detection_score > self.fusion_decision_engine.threshold:
            self.alert_system.trigger_deepfake_alert(raw_stream_data.source_id, detection_score, confidence)
            return "DEEPFAKE_DETECTED"
        else:
            return "CONTENT_VERIFIED"

Walkthrough of Key Modules:

StreamIngestionModule: This module acts as the frontline, designed to ingest vast quantities of real-time streaming data – video frames, audio segments, and accompanying metadata – with minimal latency. It leverages technologies like Kafka or Flink for robust stream processing.
MultiModalAnalysisEngine: This is the computational core, a sophisticated AI ensemble analyzing multiple characteristics simultaneously.
- analyze_image: Employs computer vision models to detect subtle image inconsistencies: flickering pixels, unnatural shadows, lighting mismatches, and temporal artifacts indicative of generative models.
- analyze_audio: Utilizes advanced audio processing and speech recognition to identify synthetic voice patterns, unnatural prosody, or inconsistencies in pitch and timbre that betray AI-generated speech.
- analyze_physiological_cues: A cutting-edge component focusing on micro-expressions, inconsistencies in eye movement, pupil dilation, or even subtle changes in facial blood flow – often imperceptible to the human eye, but critical indicators of a non-human source.
CryptographicProvenanceValidator: This module represents the “C2PA on steroids” concept. It actively verifies cryptographic content provenance metadata embedded within the stream. It checks digital signatures, validates the chain of custody, and confirms attributes from the original capture device. Any discrepancy or lack of verifiable provenance significantly raises a red flag.
FusionAndDecisionEngine: The brain of the operation, this module aggregates the real-time insights from all analysis components and the provenance validator. Using advanced machine learning models (e.g., Bayesian networks or deep neural networks), it calculates a composite “deepfake probability score” and a confidence level. It’s designed to make extremely rapid decisions, often in milliseconds, based on dynamically adjusted thresholds.
RealTimeAlertSystem: Upon a high-confidence deepfake detection, this module instantly triggers alerts, flagging the content within streaming platforms, social media feeds, or security dashboards, potentially initiating automatic mitigation actions.

This architectural blueprint illustrates how concurrent multi-modal analysis, combined with robust cryptographic verification, creates a powerful, real-time defense mechanism.

Conclusion

The evolution of real-time deepfake detection marks a pivotal moment in the fight for digital truth. By integrating multi-modal AI that scrutinizes every pixel and phoneme with cryptographic content provenance, we are finally equipping our digital infrastructure with the vigilance it desperately needs. This isn’t merely a technological advancement; it’s a fundamental reassertion of trust in our shared digital reality. The battle for truth in our feeds demands this level of sophisticated, instantaneous defense. It’s about ensuring that by mid-2026, the question of “is this real?” can be answered not after the damage is done, but as it happens. And frankly, it’s about damn time.