Revolut Shared Passports, Bitcoin Data After Fake Request

What Revolut Disclosed After the Fraudulent Government Request

The core claim is narrow but serious: Revolut handed over customer passports and Bitcoin transaction histories after receiving a request that was later characterized as fraudulent, as reported by Unchained. For related coverage, see Bitcoin: $85M Whale Buy Meets Fed FUD—BTC Bear Trap?.

Customer Passports and Bitcoin Transaction Histories

Two data categories are named in the account: customer passports and Bitcoin transaction histories. The available reporting does not specify whether “passports” refers to full scans, copies, or extracted identity details, and that distinction should not be assumed. For related coverage, see Bitcoin Bucks Tech Selloff Amid AI Safety Concerns.

Details Still Requiring Verification

The timing of the disclosure, the number of affected customers, the jurisdiction involved, and any formal company response are not established in the available material. There is no evidence of stolen funds, exposed private keys, or a wider system breach, and none of those should be inferred from the disclosure alone.

Questions About How the Government Request Was Verified

The request is described as fraudulent, which puts the authentication process at the center of the story. How a data holder confirms that a purported government demand is genuine, and who is authorized to release records in response, are the open reporting questions here.

Authenticating the Requester and the Request

The available account does not identify the requester, the impersonated authority, the communication channel, or the verification steps Revolut applied. Verification of the requester’s identity, their legal authority, and the scope of the request remain questions rather than confirmed failures.

Revolut’s Response and Any Confirmed Changes

No company explanation, customer notification, or remedial measure is confirmed in the material at hand. It would be premature to name a specific agency, attribute the request to a particular attacker, or assert a legal violation on the strength of the headline claim. Revolut’s broader product activity, such as its rollout of EURR in Europe, sits alongside a growing surface of customer data that any request-handling process has to protect.

Why Identity Documents and Bitcoin Histories Raise Privacy Concerns

The named data types matter because identity documents and financial records are individually sensitive and more revealing in combination. A passport ties a real-world identity to activity, and a transaction history maps that activity over time.

Potential Exposure From Combining Identity and Transaction Data

Linking a verified identity to Bitcoin transaction records could, in principle, enable identity misuse or deanonymize on-chain behavior, though these are potential risks rather than observed outcomes here. The reporting does not establish that the records contained wallet addresses, balances, counterparties, or a complete transaction history, so the scope of any exposure is unclear.

The episode fits a wider pattern in which the security of Bitcoin holders increasingly turns on off-chain systems, from custody to identity data, a theme also visible in coverage of a Bitcoin infrastructure exploit that drained Lightning payment servers and in longer-horizon concerns about a U.S. quantum hardware push affecting Bitcoin and Ethereum. Until Revolut’s verification process and the request’s origin are confirmed, this remains a single reported incident whose scale is not yet documented.

Additional source references: source document 1.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.