Skip to content
SberSpasibo Data Breach Exposes 3.3M Accounts

SberSpasibo Data Breach Exposes 3.3M Accounts

First seen 11 Nov 2026, 04:11 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 11, 2026 at 04:12 UTC
  • •3.3 million unique email addresses exposed in the SberSpasibo breach.
  • •Data includes sensitive information such as phone numbers and bank card hashes.
  • •Users are urged to change passwords and enable two-factor authentication.

In March 2023, data from СберСпасибо (SberSpasibo), the loyalty program of Russian bank Сбербанк (Sberbank), was allegedly published online, affecting 48 million users. The breach includes 3.3 million unique email addresses, phone numbers, and dates of birth. Additionally, bank card numbers were stored as unsalted SHA-1 hashes, alongside loyalty program details such as membership dates and bonus point redemptions. The breach was added to Have I Been Pwned on November 11, 2026, indicating ongoing awareness and concern about the incident. Users are advised to change their passwords and enable two-factor authentication where possible. The breach highlights significant vulnerabilities in data protection practices at financial institutions.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2023-03-01
Data breach occurred
Data from СберСпасибо was allegedly published online, impacting 48 million users.
Redpacketsecurity
2026-11-11
Breach added to Have I Been Pwned
The breach was confirmed and added to the Have I Been Pwned database, alerting affected users.
haveibeenpwned.com

More articles in this cluster (3)

Following this threat?

Track Sberbank in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What types of data were exposed?
The breach exposed email addresses, phone numbers, dates of birth, and bank card numbers stored as unsalted SHA-1 hashes.
When did the breach occur?
The breach occurred in March 2023, with data published online.
What should affected users do?
Affected users should change their passwords and enable two-factor authentication on their accounts.