Join our Newsletter — 33% off our NHI Course

Why are Revolut and Swiss Bitcoin Pay breaches exposing data?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: The breaches show that social engineering can defeat trusting identity checks in Web3 workflows, according to FYEO. Exposed customer records then become reusable material for phishing and fraud, so access paths need tighter approval and verification.

Editorial analysis by NHI Mgmt Group, based on content published by FYEO: “Data Breach Alert: Revolut and Swiss Bitcoin Pay…”.

By the numbers:

  • Revolut said nearly 700 customers were affected by the data exposure, according to FYEO.

Key questions

Q: Why does exposed customer identity data create so much fraud risk even when attackers cannot log into the account?

A: Exposed identity data enables convincing impersonation.

Q: What are the signs that a trusted request workflow is failing?

A: Look for approvals that rely on sender identity alone, exceptions handled outside standard channels, and staff who cannot explain why a disclosure was approved.

Q: How should security teams stop social engineering from turning into data disclosure?

A: Treat any request for sensitive personal or financial data as a privileged event.

Practitioner guidance

  • Implement out-of-band verification for sensitive requests Require a second channel and a second approver before any release of customer identity or financial data, especially when the request claims regulatory authority.
  • Classify data release as a privileged workflow Treat disclosure of passports, transaction histories, IBANs, and similar records as a privileged action with approval logging and exception review.
  • Reduce the retained data footprint Keep only the customer attributes required for operations and shorten retention where business or regulatory needs allow.

Bottom line: These breaches show that social engineering can bypass technical controls when identity verification workflows are too trusting.

Glossary terms: Social Engineering, Pretexting, Operational security, Data Minimization

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 2 weeks ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Social engineering has become an identity governance failure, not just a training problem. These incidents show that attacker success depends on whether an organisation can distinguish legitimate authority from manufactured authority. When approval pathways rely on familiarity, email legitimacy, or urgency, the control environment is already weakened. Practitioners should treat request validation as part of identity security, not as a soft process concern.

A few things that frame the scale:

  • 59% of compromised machines in a major 2025 supply chain attack were CI/CD runners rather than personal workstations, according to the State of Secrets Sprawl 2026.
  • 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: What should teams do when a third-party or support channel can access customer records?

A: Reassess the workflow as if it were an external privilege path. Limit the data exposed through that channel, enforce least privilege, and require explicit ownership for every access route that can reveal regulated or sensitive information.

👉 Read our full editorial: Social engineering is exposing Web3 platforms to data breaches


This post was modified 2 weeks ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.