12 September 2026
Revolut customers began receiving breach notifications on September 11–12, 2026, disclosing that identity documents, KYC verification selfies, IBANs, and complete transaction histories (including Bitcoin) were exposed — not through a hack, but because Revolut fulfilled a fraudulent request that impersonated a government agency and passed SPF, DKIM, and DMARC email authentication. This video combines and cross-checks the original technical analysis with independent reporting and blockchain investigator ZachXBT's findings on likely scope. It also covers what's still unconfirmed: the exact number of affected customers, which government agency was impersonated, and whether other institutions received the same fraudulent request. Timestamps: 00:00 Intro 00:21 The attack vector 00:52 What was taken 01:17 Revolut's customer notification (quoted) 01:43 Why this defeats normal defenses 02:13 The Bitcoin problem 02:41 Scope: smaller than it sounds? 03:08 What Revolut said publicly 03:30 Not Revolut's first incident 04:07 If you're affected — a checklist 04:38 What's still unconfirmed 05:15 Outro Sources: thecybersecguru.com (primary technical analysis, quoting Revolut's customer notification in full) — cross-checked against independent reporting confirming the SPF/DKIM/DMARC detail and ZachXBT's scope assessment ("targeted at high net worth users," "likely limited in size"). IMPORTANT: Several key facts remain unconfirmed at time of publishing — the number of affected customers, the identity of the impersonated government agency, and whether other institutions were targeted by the same fraudulent mailbox. Revolut's only public statement to date does not add detail beyond acknowledging the concern. Treat specifics as credible but still developing.
No comments:
Post a Comment