Sexclub.ru data breach

313,331 records Breach date: July 2021

Exposed data

Email addressesUsernamesPasswordsIP addresses

In July 2021, Sexclub.ru suffered a data breach. The dataset indexed by LeakCheck contains 313,331 records.

The leaked records include email addresses, usernames, passwords and IP addresses.

If your data appears in this dataset, any account that shares the same password is at risk. Run a free check below, and if you find yourself in a leak — change the affected passwords and enable two-factor authentication.

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.

Sexclub.ru breach: questions and answers

When did the Sexclub.ru data breach happen?

The Sexclub.ru breach dates to July 2021.

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

LeakCheck has indexed 313,331 records from the Sexclub.ru breach.

What data was exposed in the Sexclub.ru breach?

The leaked records include email addresses, usernames, passwords and IP addresses.

Were passwords exposed in the Sexclub.ru breach?

Yes. The indexed Sexclub.ru records include passwords, in plain text or hashed. If you had an account, change that password and every other password you reused.

How do I check if my data was in the Sexclub.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 Sexclub.ru breach — and in any of the other 1,468 sources LeakCheck indexes.

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

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