BitcoinTalk.org logo

BitcoinTalk.org data breach

72,095 records Breach date: May 2015

Exposed data

Email addressesPasswords

In May 2015, BitcoinTalk.org suffered a data breach. The dataset indexed by LeakCheck contains 72,095 records.

The leaked records include email addresses and passwords.

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.

BitcoinTalk.org breach: questions and answers

When did the BitcoinTalk.org data breach happen?

The BitcoinTalk.org breach dates to May 2015.

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

LeakCheck has indexed 72,095 records from the BitcoinTalk.org breach.

What data was exposed in the BitcoinTalk.org breach?

The leaked records include email addresses and passwords.

Were passwords exposed in the BitcoinTalk.org breach?

Yes. The indexed BitcoinTalk.org 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 BitcoinTalk.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 BitcoinTalk.org breach — and in any of the other 1,469 sources LeakCheck indexes.

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

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