Fact-check findings
What an automated fact-checker found when it re-read Revolut Data Breach (Fake Government Request, September 2026) against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
2 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in section: Incident Overview
“Revolut stated that approximately 680 customers were affected, that its internal systems remained secure, and that customer funds were not at risk.”
reviewerRevolut stated that approximately 680 customers were affectedThe 680 figure comes from the threat actors and press (SecurityWeek 'understands'), not a Revolut statement. Attributing it to Revolut is wrong.Proposed correction (not yet applied)Revolut stated that a limited number of customers were affected (media reports, citing the threat actors and other sources, put the figure at approximately 680), that its internal systems remained secure, and that customer funds were not at risk. - #2[disputed][awaiting moderator]in the summary
“On September 12, 2026, Revolut confirmed that an unauthorized third party had obtained sensitive data belonging to approximately 680 customers”
reviewerRevolut confirmed on Sept 12 that data of approximately 680 customers was obtainedSame attribution error as in sections[0]; the 680 number was not part of Revolut's Sept 12 confirmation.Proposed correction (not yet applied)On September 12, 2026, Revolut confirmed that an unauthorized third party had obtained sensitive data belonging to a limited number of customers (reported by media as approximately 680)
unverifiable
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #3[unverifiable][awaiting moderator]in section: Incident Overview
“specifically the Prefecture of Reggio Calabria”
reviewerEmail account linked to Prefecture of Reggio CalabriaNot found in the two cited sources I read (Security Affairs was not checked); the timeline attributes it to Irish Times, which does not say it. - #4[unverifiable][awaiting moderator]in the timeline
“ZachXBT flagged the customer notification on the same day and assessed it as a targeted high-net-worth operation.”
reviewerZachXBT flagged the notification and assessed it as targeted high-net-worth operationNeither cited source mentions ZachXBT; The Block (cited) was not read. - #5[unverifiable][awaiting moderator]in the timeline
“2026-09-11”
reviewerCustomers began receiving notification emails on Sept 11The cited source gives no notification date.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #6[partially supported][awaiting moderator]in section: Targeted Nature of the Operation and Victim Profile
“Revolut also disclosed data belonging to residents of 33 countries in total”
reviewerAffected data included 33 countries in totalConsistent with the source arithmetic and hedged as the actors' claim. - #8[partially supported][awaiting moderator]in the timeline
“Approximate start of the fraudulent data request campaign, based on reporting that the operation ran for approximately five months before discovery.”
reviewerStart date 2026-04-01 for the campaignThe date is the page's own inference and is labeled approximate; the source gives only a duration.
confirmed
1 claimThe cited evidence supports the claim as written.
- #7[confirmed][no action needed]in section: Attack Method and Technical Mechanism
“Cybersecurity firm Hudson Rock reportedly identified approximately 300 compromised pec.interno.it webmail credentials in its cybercrime database”
reviewerOperation ran about five months; Hudson Rock found about 300 compromised pec.interno.it credentials and assessed attackers likely bought existing logs; hackers claimed 147GBThe five-month duration is reported as alleged; the page hedges adequately.