Rubukkit.org logo

Rubukkit.org data breach

98,956 records Breach date: November 2016 no passwords

Exposed data

Email addressesUsernames

In November 2016, Rubukkit.org suffered a data breach. The dataset indexed by LeakCheck contains 98,956 records.

The leaked records include email addresses and usernames.

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.

Rubukkit.org breach: questions and answers

When did the Rubukkit.org data breach happen?

The Rubukkit.org breach dates to November 2016.

How many records were leaked in the Rubukkit.org breach?

LeakCheck has indexed 98,956 records from the Rubukkit.org breach.

What data was exposed in the Rubukkit.org breach?

The leaked records include email addresses and usernames.

Were passwords exposed in the Rubukkit.org breach?

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

What should I do if my data was in the Rubukkit.org breach?

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