Entities

Entities collected from this article, grouped for quick reference and copying. Inclusion does not establish malicious activity. Article links appear separately at the bottom as references.

Revolut just handed a stranger its customers’ passports, selfies, and full transaction histories. Nobody broke in. It was one of the oldest tricks in the book, social engineering, the Kevin Mitnick approach. The threat actor simply asked, using a government email address, and Revolut said yes without blinking.

As a Revolut customer myself, I find this concerning AF. Why is the bank handing over customer data without question? There ought to be some due diligence before blindly handing out personally identifiable information to any government.

This was not a hack. There was no intrusion, no exploit, and no malware. A fraudster simply sent requests for customer information from a legitimate government agency email domain. Revolut, seeing what looked like an official government request, fulfilled it without question. Does Revolut not have in-house lawyers? Or, at worst, AI for some level of legal counsel?

The entire attack was an email and a lie.

Look at what the email pried loose. Full know-your-customer (KYC) files. Names, dates of birth, addresses, and phone numbers. Copies of passports and driver’s licenses. Verification selfies. Account statements, IBANs, withdrawal records, and complete transaction histories, Bitcoin included. Everything a bank collects to prove you are you, handed to someone pretending to be the government.

Threat actors generally have to break something. They need a vulnerability, a stolen password, a phishing click, or some technical foothold. This threat actor needed none of it. It was pure social engineering, the old-fashioned way.

All it needed was the trust most companies almost automatically extend to a request appearing to come from the government. The trust is the vulnerability, and no software patch fixes it.

This is not just a Revolut problem. It is an industry-wide issue. Law enforcement calls these emergency data requests (EDRs). They are a legitimate legal mechanism letting police or agencies ask a company for user data urgently. In a genuine emergency, these requests can bypass the normal warrant or subpoena process because exigent circumstances are allegedly at stake.

The FBI warned back in 2024 criminals were buying and compromising real government email accounts specifically to forge these requests. The exact scam hitting Revolut was flagged as a growing threat two years ago, and it still worked.

Consider the asymmetry. To get your data the legal way, a government needs process, oversight, and sometimes a judge. To get it the fraudulent way, a threat actor needs one compromised .gov inbox and the balls to ask. The trust letting law enforcement move fast in a real emergency is the same trust a criminal exploits to move fast in a fake one. The feature and the vulnerability are the same thing.

The threat actor posted the stolen data in Telegram channels. It reportedly included CEOs, athletes, and performers. It is plausible this was not some random pull, but something targeted, possibly reconnaissance on specific high-value people using Revolut as the unwitting supplier. I find this truly unsettling. This may not have been data stolen to dump or sell, but data extracted for targeting.

The average customer is left mostly powerless. You did everything right. You gave your bank your ID because you had to. The failure was not yours. It was one person inside a company deciding a convincing email was authorization enough.

Every regulated firm should be forced to answer a simple question. Who inside your walls can release a complete file on a customer, and on whose word? At Revolut, the answer turned out to be anyone with a government email address and a good story.

Customers were never really trusting their bank to guard their identity. They were trusting no one would ever ask for it convincingly enough. Revolut did not lose control of the vault. Someone knocked on the front door wearing a government badge, asked for the contents, and Revolut carried the boxes outside, a breach it would soon see claimed in public.

The breach was not technical. The authorization was.