Sberpravo data breach

70,944 records Breach date: February 2023 no passwords

Exposed data

Email addressesUsernamesNamesDates of birth

In February 2023, Sberpravo suffered a data breach. The dataset indexed by LeakCheck contains 70,944 records.

The leaked records include email addresses, usernames, names and dates of birth.

The indexed records do not include passwords, but the details they hold can still be used for phishing. Run a free check below to see whether you are affected.

Check if your account is affected

Enter your email, username or phone number — the check is free and confidential, and the result will tell you whether this breach mentions you.

Exposed in this breach? Do this now

Change the password

On the breached site and everywhere else you reused it. Make every password unique.

Enable 2FA

A second factor keeps a leaked password from becoming a hijacked account.

Set up monitoring

and get notified the moment your data appears in a new leak.

Sberpravo breach: questions and answers

When did the Sberpravo data breach happen?

The Sberpravo breach dates to February 2023.

How many records were leaked in the Sberpravo breach?

LeakCheck has indexed 70,944 records from the Sberpravo breach.

What data was exposed in the Sberpravo breach?

The leaked records include email addresses, usernames, names and dates of birth.

Were passwords exposed in the Sberpravo breach?

No. The records indexed from Sberpravo do not include passwords — but the other details they hold can still be used for phishing.

How do I check if my data was in the Sberpravo breach?

Enter your email address, username or phone number in the search form on this page. The free check shows whether your data appears in the Sberpravo breach — and in any of the other 1,469 sources LeakCheck indexes.

What should I do if my data was in the Sberpravo breach?

Change the password you used on Sberpravo and everywhere you reused it, turn on two-factor authentication, and watch for phishing that quotes details from the leak. To hear about the next breach first, set up breach monitoring.