Skip to content

Invest Independently confirmed2 publishers 3 min read Published Updated

A compromised government email account pulled about 680 customer files out of Revolut over months

Revolut answered fraudulent information requests sent from a real government email account for months. A group calling itself iamnotavillain now wants about $3 million in Monero for the roughly 680 customer files.

The Investor · Invest desk

Send a correction

What happened

  • Revolut disclosed on 12 September 2026 that an unauthorized party had used an email account on a genuine government-agency domain to send it fraudulent information requests.
  • The bank treated those messages as official legal demands and supplied customer records in response over a period of months before the deception was identified.
  • A source familiar with the matter put the affected population at roughly 680 customers, many of them selected because of suspected cryptocurrency activity, out of tens of millions of users.
  • A group calling itself iamnotavillain demanded about $3 million in Monero within 24 hours, and a Revolut spokesperson told Reuters the bank had received no direct contact or demand from it.

Why it matters

  • What it costs cost The demand comes to roughly $4,400 for each of about 680 customers, a per-head price for files the group already holds, with the funds untouched and the systems intact.
  • What it limits constraint Revolut cannot close this hole by declining law-enforcement requests, because regulated firms must answer legitimate ones; the only place left to add a check is the demand itself, and that slows every response.
  • Who's exposed exposure Customers whose identity documents and Bitcoin histories were handed over face targeted fraud and further extortion attempts, and that risk survives whatever the bank pays.
  • What it sets up precedent Both the group and the bank say there was no private contact before the public countdown, so the pressure was applied through the press and the customers; any firm with a legal-request inbox is reachable the same way.

The control that failed is the one that reads a legal demand and decides whether the authority behind it is real. Revolut's checks looked at the sender, and the sender was an email account on a genuine government-agency domain [2]. The messages passed as official legal demands and the bank answered them over a period of months [3]. The duration matters more than the first request: the queue kept answering one address for months, and the check it ran each time stopped at the sender [11].

Roughly 680 customers were affected, according to a person familiar with the matter [4], and the public demand was about $3 million in Monero inside 24 hours [5]: about $4,400 a customer [21]. Revolut says no funds were taken and that its systems, databases and customer accounts were not penetrated [15][14]. The $3 million buys a promise not to resell the files to other criminal groups [5].

Many of the accounts appear to have been picked because of suspected cryptocurrency activity [6]. The group told the Financial Times it chose targets through blockchain analysis and had used a compromised Italian government email system to pose as law enforcement [8]. The material that left the company included passport and driving licence copies, verification photographs, IBANs and transaction histories with Bitcoin activity [7]. Per the report, the practical danger for those customers is targeted fraud or further extortion attempts, and that danger sits outside whatever Revolut decides about the payment [20].

The report points to how financial firms check the substance of legal demands even when the sending infrastructure looks genuine [12]. Regulated firms have to answer legitimate government and law-enforcement requests [10]. That leaves one place to add a check: an out-of-band callback on every demand, paid for in compliance handling time.

If Revolut pays nothing and the records circulate, the cost falls on those 680 people and on the Italian authorities now examining the compromise of the government email accounts [18]. The regulators the bank notified itself, data-protection authorities and financial supervisors among them [9], could instead treat a months-long response window as a control failure. Then the number stops being $3 million and becomes whatever they assess. A third possibility is that the group holds less than it says.

In my view the supervisory question is the more expensive one. The money named in the public countdown is $3 million [5], while the response window the bank has already reported to its own regulators is measured in months [3][9]. A supervisory finding that answering an authenticated government domain met the standard of care would prove that wrong. It would move the failure onto Italy's compromised email accounts [18].

What to watch

  • Whether Italian investigators identify other banks and payment firms that answered requests from the same compromised accounts.
  • Whether Revolut's affected-customer total stays near 680 once the full history of fraudulent requests is reconstructed.
  • Whether any of the files surface for sale, which would be the first independent test of the group's claim to hold them.

Information, not investment advice. This story is general information about companies and markets, drawn from cited reporting. It is not a recommendation to buy, sell or hold any security; check the cited sources before acting.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence62
Adoption
Not scored
Hype gap+8
Incentives55
Confidence60
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Revolut first disclosed the customer-data problem on 12 September 2026.

    Reported SupportedView cited source
  2. [2]

    An unauthorized party used an email account on a genuine government-agency domain to send fraudulent information requests to Revolut.

    Reported SupportedView cited source
  3. [3]

    Revolut treated those messages as official legal demands and supplied records over a period of months.

    Reported SupportedView cited source
  4. [4]

    A source familiar with the matter said the episode involved roughly 680 customers rather than a mass compromise of the platform's tens of millions of users.

    Reported SupportedView cited source
  5. [5]

    Days after the disclosure, a group using the name iamnotavillain published an online demand for payment equivalent to about $3 million in Monero within 24 hours, and threatened to sell the records to other criminal groups if the money was not paid.

    Reported SupportedView cited source
  6. [6]

    Many of the affected accounts appear to have been selected because of suspected cryptocurrency activity.

    Reported SupportedView cited source
  7. [7]

    The material that left the company included names, dates of birth, postal and email addresses, phone numbers, copies of passports and driving licences, verification photographs, account statements, IBANs and transaction histories, including Bitcoin activity.

    Reported SupportedView cited source
  8. [8]

    The Financial Times reported that the group said it had used a compromised Italian government email system to pose as law enforcement and that it had chosen targets through blockchain analysis.

    Reported SupportedView cited source
  9. [9]

    Once the deception was identified, Revolut blocked the address and notified the relevant government body, law enforcement, data-protection authorities and financial regulators, and contacted the customers involved.

    Reported SupportedView cited source
  10. [10]

    Banks and payment firms are required to respond to legitimate government and law-enforcement requests.

    Reported SupportedView cited source
  11. [11]

    When requests arrive from an authenticated official domain, technical checks can still pass.

    Reported SupportedView cited source
  12. [12]

    The incident raises questions about how financial firms verify the substance of legal demands even when the sending infrastructure looks genuine.

    Reported SupportedView cited source
  13. [13]

    Revolut has described the episode as a sophisticated impersonation scam rather than a conventional hack of its infrastructure.

    Reported SupportedView cited source
  14. [14]

    Revolut has stressed that its own systems, databases and customer accounts were not penetrated.

    Reported SupportedView cited source
  15. [15]

    Customer funds were not taken.

    Reported SupportedView cited source
  16. [16]

    The group told the Financial Times it had not negotiated privately with Revolut and was using the website to make its first public demand.

    Reported SupportedView cited source
  17. [17]

    A Revolut spokesperson told Reuters that the company had received no direct contact or demand from the individuals or group making the claims.

    Reported SupportedView cited source
  18. [18]

    Italian authorities have begun examining the reported compromise of government email accounts.

    Reported SupportedView cited source
  19. [19]

    As of mid-September 2026 there was no independent confirmation that the records had been sold after the public deadline passed.

    Reported SupportedView cited source
  20. [20]

    For customers whose identity documents and transaction histories were handed over, the practical danger is targeted fraud or further extortion attempts that sit outside any payment the company itself might or might not make.

    Reported SupportedView cited source
  21. [21]

    The roughly $3 million demand works out to about $4,400 for each of the roughly 680 affected customers.

    Derived Supported

Sources

2 independent publishers whose own reporting we read for this story.

  1. americanbanker.com

    1 article · September 18, 2026

    Revolut's breach began with a stolen government password
  2. crowdfundinsider.com

    1 article · September 19, 2026

    Digital Bank Revolut Denies Direct Contact From Group Claiming Data Breach Ransom

Topics and entities

Topics

Entities