Wallet.btc.com data breach

12,488 records Breach date: unknown

Exposed data

Email addressesPasswords

Wallet.btc.com suffered a data breach; the exact date of the incident is unknown. The dataset indexed by LeakCheck contains 12,488 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.

Wallet.btc.com breach: questions and answers

When did the Wallet.btc.com data breach happen?

The exact date of the Wallet.btc.com breach is not known.

How many records were leaked in the Wallet.btc.com breach?

LeakCheck has indexed 12,488 records from the Wallet.btc.com breach.

What data was exposed in the Wallet.btc.com breach?

The leaked records include email addresses and passwords.

Were passwords exposed in the Wallet.btc.com breach?

Yes. The indexed Wallet.btc.com 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 Wallet.btc.com 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 Wallet.btc.com breach — and in any of the other 1,468 sources LeakCheck indexes.

What should I do if my data was in the Wallet.btc.com breach?

Change the password you used on Wallet.btc.com 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.