VBForums.com logo

VBForums.com data breach

192,054 records Breach date: June 2016

Exposed data

Email addressesUsernamesPasswords

In June 2016, VBForums.com suffered a data breach. The dataset indexed by LeakCheck contains 192,054 records.

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

VBForums.com breach: questions and answers

When did the VBForums.com data breach happen?

The VBForums.com breach dates to June 2016.

How many records were leaked in the VBForums.com breach?

LeakCheck has indexed 192,054 records from the VBForums.com breach.

What data was exposed in the VBForums.com breach?

The leaked records include email addresses, usernames and passwords.

Were passwords exposed in the VBForums.com breach?

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

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

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