A Revolut data breach has exposed the two things a crypto holder least wants paired: identity documents and transaction histories. Revolut disclosed that attackers extracted customer KYC files, passport scans, full names, physical addresses, email addresses, and phone numbers, along with complete historical Bitcoin and crypto transaction ledgers, after tricking the fintech's compliance staff with a fake law enforcement data request sent from a compromised mailbox on an authentic government domain. The domain was real, so standard email authentication passed, and the legal process looked like the kind banks comply with every week. The company confirmed the incident was "a sophisticated external impersonation scam where an unauthorised third party utilised a legitimate government domain."
Two facts shape the severity. First, no funds, account balances, passwords, PINs, or banking credentials were accessed. Second, the target list was not random: a limited number of high-net-worth crypto users were selected, which means whoever ran this operation now holds a targeting package, identity documents linked to known crypto balances and full transaction histories, for the exact demographic that physical seed-phrase robbery crews and sophisticated phishing operations monetize.
How the Revolut Data Breach Beat Email Security
The mechanics deserve close attention, because they defeat the defenses most companies trust. The attackers did not spoof a government domain, which SPF and DKIM would catch; they used a genuine domain with a compromised mailbox inside it, so the email genuinely originated from legitimate government infrastructure. Revolut's compliance process then did exactly what a regulated financial institution is required to do when presented with legal process: it verified the domain, saw a government sender, and disclosed the requested files. The failure was not carelessness but architecture, an implicit assumption that a request arriving from a government domain is a lawful request. That assumption is now dead. The same trust-in-header failure pattern has surfaced elsewhere, notably in the Brevo SSO breach behind the Trezor phishing wave, where authenticated infrastructure, not spoofed infrastructure, was the attack vector, and in Bits of Gold's customer data probe, where broker databases proved to be the soft target. Even state-driven data demands against exchanges now read differently: the industry can no longer distinguish legitimate process from hostile process by looking at the sender.
Why KYC Plus Transaction History Is the Dangerous Pair
Separately, a passport scan is an identity theft risk and a transaction ledger is a privacy leak. Together they are a physical security threat: an attacker who knows who you are, where you live, and what your wallet history looks like can mount targeted extortion, fake-authority phishing with credible details, or the home-invasion playbook. That is why the high-net-worth targeting pattern is the worst detail in the disclosure, and why Revolut's refusal to publish the affected headcount, and its withholding of the specific government domain due to an ongoing federal investigation, matter: customers cannot self-assess their exposure until the scope is named.
The Fix Nobody Has Shipped Yet
The industry answer to forged legal process already exists conceptually: out-of-band verification, where a data request received by email is confirmed through a second authenticated channel, a phone attestation to the requesting agency, a government portal login, or cryptographic request signing, before any file moves. No major fintech has made it standard. Regulators, including the UK Information Commissioner's Office, which Revolut notified, now have a live case study for why legal-response workflows need the same anti-phishing engineering as customer login flows. Watch for the ICO's determination, the eventual naming of the compromised government domain, and whether any major bank announces verified-channel legal process in the next quarter. The next breach will use the same mailbox. The question is whether anyone will have closed it.













































