Revolut Suspected of Leaking Customer Data After Fake Government Request – BitRss

---

Key Facts

• Revolut is suspected of responding to a spoofed government data request with real customer records.
• Exposed data reportedly includes identity documents and Bitcoin transaction histories tied to affected accounts.
• The company has not published a dedicated public statement detailing the incident as of this writing.

Revolut is suspected of handing over customer identity documents and Bitcoin transaction records after receiving a data request that impersonated a government agency, rather than one that actually came from it. If confirmed, the failure sits in a specific and well-understood category: not a hack of Revolut’s systems, but a breakdown in how the company verified who was asking for data before it handed that data over.

Why This Failure Mode Is Different From a Breach

A traditional data breach means an attacker got past technical defenses, exploiting a vulnerability in code or infrastructure to pull data out. What is being described here is a social engineering failure: a request formatted and worded to look like it came from law enforcement or a regulator, sent through channels the company treats as legitimate by default. Financial institutions maintain expedited processes for genuine government requests precisely because law enforcement sometimes needs records quickly, and that same speed is exactly what a convincing forgery is designed to exploit. The fix for this category of failure is procedural, verifying the requesting agency’s identity independently before responding, not technical in the way a software patch would be.

The specific data reportedly exposed matters more than a generic reference to “customer data” would suggest. Identity documents are the raw material for account takeover and further impersonation fraud. Bitcoin transaction histories tied to a real identity are a more unusual and more sensitive category of leak, since they can connect a named individual to specific wallet activity that the person may not have expected to ever be tied back to them, exposure that has follow-on risk beyond typical financial fraud.

What Would Actually Confirm the Story

As of this writing, Revolut had not published a dedicated statement on this specific incident through its own official channels, including its newsroom or its published guidance on protecting accounts from scams. That absence is itself notable for a company of Revolut’s size and regulatory footprint, since a confirmed breach of this kind typically triggers mandatory notification obligations under data protection law in the jurisdictions where it operates. Anyone who believes their Revolut account information may have been affected can report concerns directly through the company’s own fraud and cybercrime reporting directory, which lists the relevant national authority for each market. Until Revolut or a national data protection regulator issues a formal finding, the specifics of what was accessed and how many accounts were affected remain unconfirmed.

This post first appeared in Revolut Suspected of Leaking Customer Data After Fake Government Request