Rabota-v-sochi data breach

11,684 records Breach date: January 2013 no passwords

Exposed data

NamesPhone numbers

In January 2013, Rabota-v-sochi suffered a data breach. The dataset indexed by LeakCheck contains 11,684 records.

The leaked records include names and phone numbers.

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.

Rabota-v-sochi breach: questions and answers

When did the Rabota-v-sochi data breach happen?

The Rabota-v-sochi breach dates to January 2013.

How many records were leaked in the Rabota-v-sochi breach?

LeakCheck has indexed 11,684 records from the Rabota-v-sochi breach.

What data was exposed in the Rabota-v-sochi breach?

The leaked records include names and phone numbers.

Were passwords exposed in the Rabota-v-sochi breach?

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

What should I do if my data was in the Rabota-v-sochi breach?

Change the password you used on Rabota-v-sochi 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.