Lavaguden.ru logo

Lavaguden.ru data breach

11,098 records Breach date: January 2019 no passwords

Exposed data

UsernamesIP addresses

In January 2019, Lavaguden.ru suffered a data breach. The dataset indexed by LeakCheck contains 11,098 records.

The leaked records include usernames 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.

Lavaguden.ru breach: questions and answers

When did the Lavaguden.ru data breach happen?

The Lavaguden.ru breach dates to January 2019.

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

LeakCheck has indexed 11,098 records from the Lavaguden.ru breach.

What data was exposed in the Lavaguden.ru breach?

The leaked records include usernames and IP addresses.

Were passwords exposed in the Lavaguden.ru breach?

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

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

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