
Revolut Fell for Fake Government Emails: Passport Selfies and Bitcoin Transaction History Stolen
Written by: Boaz Sobrado, Forbes
Translated by: AididiaoJP, Foresight News
UK fintech company Revolut confirmed that it recently disclosed some customers' identity documents and transaction records to a third party impersonating government officials after mistakenly trusting an email disguised as a government subpoena request. The incident was not a system breach, and there is no evidence that customer accounts were accessed by unauthorized parties; Revolut proactively submitted the data as part of a "government request" process.
Affected customers began receiving notifications around September 11, 2026. Former Mt.Gox CEO Mark Karpès publicly shared the email he received, which had the subject line "Urgent Security Update Regarding Your Revolut Account." On-chain investigator ZachXBT subsequently reposted the content on his Telegram channel, noting that the scope of impact appears limited and the targets seem to align more with high-net-worth individuals.
According to disclosures, the sender address of the involved email was hosted on a legitimate government domain and held valid domain authentication credentials, successfully passing SPF, DKIM, and DMARC checks. For banks and licensed payment institutions, these technical validations are typically used to verify whether an email genuinely originates from the claimed institution. Consequently, Revolut treated it as a legitimate law enforcement or regulatory request and submitted the data. It was only after the company verified with the alleged government agency that it discovered the email was neither owned nor used by authorized personnel.
Revolut promptly blocked the address internally and notified relevant government agencies, law enforcement, and data protection and financial regulators, while simultaneously notifying affected customers. A spokesperson told media outlets that this was a "complex external impersonation scam" and emphasized that "Revolut's systems and customer funds remain unaffected." The company did not disclose the name of the agency that was impersonated, nor did it release the exact number of affected individuals or market reach, only stating that a "limited number of customers" have been contacted directly.
The potentially compromised data outlined in the notice is far more comprehensive than typical credential stuffing breaches. Identity information includes full name, date of birth, and occupation; contact details cover home address, email address, and phone number; identification documents include copies of passports or driver's licenses, along with facial verification selfies submitted during account opening. The company specifically noted that biometric templates used for matching (facial telemetry) were not disclosed, but the original selfie images were included. Financial information encompasses account statements, IBANs, account status, account opening dates, internal wallet reference numbers, and complete transaction histories, explicitly including Bitcoin purchase, sale, and withdrawal records. At present, there are no indications that private keys, login passwords, card PINs, or account balances were also submitted, and there are no public reports of stolen funds.
For crypto users, the danger of this dataset lies not in immediate fund transfers, but in the direct linking of on-chain activity to real-world identities. Passport photos, addresses, IBANs, combined with complete deposit and withdrawal records and wallet reference numbers, are sufficient for targeted phishing, impersonating customer support to perform account recovery, or conducting reverse on-chain analysis using real names. ZachXBT warned that leaked lists and addresses have previously been linked to offline incidents targeting coin holders.
Revolut has characterized the incident as an external impersonation attempt rather than a production system intrusion. Based on available public information, the attacker exploited a procedural loophole where financial institutions must respond to government requests: because the email originated from a legitimate domain and passed authentication checks, internal review protocols treated it as a genuine request. Karpès and others have publicly urged the company or the impersonated agency to reveal the organization's name so that other banks and exchanges can investigate similar requests using the same email address. As of press time, no party has named the entity.
It should be noted that several past Revolut incidents differ from this one. In 2022, Lithuania's data protection authority documented approximately 50,150 customers affected by social engineering attacks targeting employees. In July 2026, a dark web marketplace claimed to be selling 75 million Revolut records, though internal company verification suggested they were likely forged. Earlier that same year, in February, the company reported a former employee to law enforcement for allegedly extorting the business with KYC data. None of these events are related to the current "fake government email request" incident.
For customers who have received notifications, the most realistic risk is secondary fraud. Armed with passport photos, addresses, and transaction details, malicious actors can easily send follow-up "official remediation" emails or make calls demanding verification codes, recovery mnemonics, or transfers of cryptocurrency into so-called "secure wallets." Revolut's advice remains unchanged: communicate only through the in-app chat feature, do not click suspicious links, and avoid answering unexpected calls that immediately reference this breach.
Several questions remain unresolved: exactly how many individuals' data was submitted, which agency in which country was impersonated, when the request was submitted and when the data was dispatched, whether the same email address was used to target other licensed institutions, and whether the third party continues to utilize the obtained data. Without filling these gaps, other platforms will struggle to conduct targeted audits.
This incident once again brings an old issue to the forefront: regulators require platforms to collect passports, selfies, and complete transaction histories, but once these files are tricked out via requests with "legitimate appearance," the resulting damage is often more severe and harder to contain than a standard credential stuffing attack. The system was not breached, funds remain secure in accounts, but the layer of information that ties customer identities to Bitcoin transaction flows has already been exposed.















