Kassy.ru logo

Kassy.ru data breach

4,546,033 records Breach date: April 2023 no passwords

Exposed data

Email addressesNamesPhone numbersIP addresses

In April 2023, Kassy.ru suffered a data breach. The dataset indexed by LeakCheck contains 4,546,033 records.

The leaked records include email addresses, names, phone numbers and IP addresses.

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.

Kassy.ru breach: questions and answers

When did the Kassy.ru data breach happen?

The Kassy.ru breach dates to April 2023.

How many records were leaked in the Kassy.ru breach?

LeakCheck has indexed 4,546,033 records from the Kassy.ru breach.

What data was exposed in the Kassy.ru breach?

The leaked records include email addresses, names, phone numbers and IP addresses.

Were passwords exposed in the Kassy.ru breach?

No. The records indexed from Kassy.ru 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 Kassy.ru 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 Kassy.ru breach — and in any of the other 1,469 sources LeakCheck indexes.

What should I do if my data was in the Kassy.ru breach?

Change the password you used on Kassy.ru 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.