Revolut data breach: the reported fake government request
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
Reuters reported in September 2026 that Revolut disclosed customer information to an unauthorised third party after fraudulent data requests were sent from a compromised email domain associated with an Italian Interior Ministry office, while Revolut said its systems and customer funds were unaffected. Italy’s government told parliament that data on 680 customers, including eight Italians, had been provided, potentially including identity and contact details, document copies, selfies, account statements, and transaction histories. The incident illustrates risks surrounding anti-money-laundering and know-your-customer records, which financial firms are generally required to retain for five years after a customer relationship ends, alongside GDPR rules under which unauthorised disclosure may constitute a personal data breach requiring regulator and customer notifications depending on the risk. As of 6 October 2026, no regulatory finding or sanction had been published, although UK, Italian, and Lithuanian authorities were reportedly assessing or discussing the matter. The account emphasizes that valid email-domain authentication does not prove a requester’s authority and argues that firms should independently verify requests, limit disclosures to necessary data, maintain review procedures, and document decisions.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.