Revolut Data Breach Via Fake Government Requests – What We Know So Far
Revolut confirmed attackers extracted customer KYC records by sending fraudulent data requests from a spoofed or compromised government agency email domain.
Revolut confirmed a data breach in which an unauthorized party obtained sensitive customer records by submitting fraudulent information requests from an email account on a legitimate government agency domain with valid SPF/DKIM/DMARC authentication. Disclosed data could include full names, dates of birth, passport or driving-license copies, onboarding facial images, IBANs, account statements, withdrawal records, and complete transaction histories including Bitcoin activity. Crypto investigator ZachXBT assessed the operation targeted high-net-worth users, while a threat actor using the name 'IAmNotAVillain' claimed Italian law-enforcement departments were compromised over six months with 147 GB of material, claims that remain unverified. Revolut says only a limited number of customers were affected, blocked the email address, and notified regulators and affected customers, stating its systems and funds were not compromised.
Revolut Confirms Data Breach Through Fake Government Requests
Revolut disclosed customers' IDs, selfies, and financial data to impostors sending fraudulent requests from a legitimate government email domain.
Revolut confirmed an unauthorized third party obtained sensitive customer records by submitting fraudulent information requests from a legitimate government agency email domain with valid domain authentication, which employees fulfilled as standard legal compliance. Exposed data reportedly includes names, dates of birth, addresses, phone numbers, email addresses, occupations, passport and driver's license copies, verification selfies, IBANs, account-opening dates, transaction and withdrawal histories, and Bitcoin wallet references. Revolut says only a 'very limited group of customers' was affected, that systems and funds were untouched, and that it blocked the address and notified the agency, law enforcement, and regulators. Researcher ZachXBT first publicized the breach via Telegram on September 12.