Revolut data breach: Dutch police foil violence on customers
Part of the Revolut story · since 19 Nov
- Thu 19 Nov, 13:42 UTC. cybersixt, first report. Revolut data breach: Dutch police foil violence on customers. This article, 1st of 1.
Dutch police say they foiled several attempts at violence in the Netherlands against Revolut customers whose data was stolen in September. “Afterwards there were several attempted violent incidents in the Netherlands that can be linked to the data theft,” the police said in a statement on Thursday (our translation), adding that the incidents took place in The Hague and Amsterdam and that several arrests were made, including of suspects of French and Belgian origin.
Police arrested ten people who planned to commit violence, the Dutch broadcaster NOS reported, and would not say how many people were targeted or what kind of violence was planned, for safety reasons. Revolut told NOS that 36 of the victims are Dutch.
How the data was taken
According to the police, unauthorised third parties obtained “identifying data” on hundreds of European Revolut customers in September. In that month, Revolut said threat actors had posed as a government agency and sent it fraudulent legal requests, which it answered, SecurityWeek reported. Revolut's notice to customers said personal information, passports, email addresses, phone numbers and financial information were compromised, according to SecurityWeek, which understood that about 680 customers were affected. Revolut did not name the agency.
A threat actor using the name “IAmNotAVillain” publicly demanded $3 million from Revolut and threatened to sell the data. The actor and the threat intelligence firm Hudson Rock said the requests came from a compromised email account of an Italian Ministry of the Interior employee; that has not been confirmed by Italian authorities or Revolut. NOS also reports that the criminals posed as an Italian government agency.
The investigation
A specialised police team is investigating the foiled incidents and their background under the authority of the Public Prosecution Service, with units in both The Hague and Amsterdam, the police said. Police and Revolut have taken measures to protect the victims: Revolut has set up “proactive, voluntary online protection measures” for them, and police have taken preventive security measures. Revolut has contacted every customer affected by the theft, according to the police.
Police and prosecutors said advanced cyber and social engineering incidents are becoming more common in every sector and urged organisations to stay alert to their digital security.
What customers can do
The police say anyone involved in this incident has already been contacted by Revolut directly. For everyone else, they advise changing the passwords of email and other important accounts, using a unique password for each account, turning on two-step verification, checking bank accounts regularly and treating messages with care even when the sender looks right or the message is addressed to the reader by name.
The police have not said what the suspects are charged with or when the violence was planned.
How the story developed
1 article from 1 outlet since 19 Nov. Still developing; the latest report was 4 hours ago. This was the first report.
- Thu 19 Nov, 13:42 UTC. cybersixt, first report. Revolut data breach: Dutch police foil violence on customers. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Thu 19 NovDay 01
- Revolut data breach: Dutch police foil violence on customers13:42 · cybersixt · First report · This article, 1st of 1
Sources
More reporting
- VMware vCenter zero-day CVE-2026-123890 exploited in September19 Nov
- N-able breach knocks Mail Assure and SpamExperts portals offline19 Nov
- European Commission cyberattack tied to AI hacking tool ARTEX19 Nov
- Ruby vulnerabilities: seven memory flaws fixed, RCE PoCs exist19 Nov
- SBC Medical data breach hits 1.6M Shonan Beauty Clinic customers19 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS