Zoloto585.ru logo

Zoloto585.ru data breach

8,941,147 records Breach date: unknown

Exposed data

NamesPhone numbersDates of birthGeographic locations

Zoloto585.ru suffered a data breach; the exact date of the incident is unknown. The dataset indexed by LeakCheck contains 8,941,147 records.

The leaked records include names, phone numbers, dates of birth and geographic locations.

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.

Zoloto585.ru breach: questions and answers

When did the Zoloto585.ru data breach happen?

The exact date of the Zoloto585.ru breach is not known.

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

LeakCheck has indexed 8,941,147 records from the Zoloto585.ru breach.

What data was exposed in the Zoloto585.ru breach?

The leaked records include names, phone numbers, dates of birth and geographic locations.

Were passwords exposed in the Zoloto585.ru breach?

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

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

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