Breach Database / vBulletin

Yes — vBulletin was breached.

What happened

In November 2015, the forum software maker vBulletin suffered a serious data breach. The attack lead to the release of both forum user and customer accounts totalling almost 519k records. The breach included email addresses, birth dates, security questions and answers for customers and salted hashes of passwords for both sources.

What data was exposed

What to do right now

  1. Change your password for this service now. And change it anywhere you reused the same password — attackers try leaked passwords on other sites within hours ("credential stuffing").
  2. Turn on two-factor authentication. Even a leaked password is useless against an account protected by a second factor. Prefer an authenticator app over SMS.
  3. Reset security questions everywhere you used the same answers. Treat leaked security answers like leaked passwords — they rarely change and unlock account recovery.
  4. Expect convincing phishing emails. Attackers use breached details to write personalized emails. Be suspicious of any message referencing this service.
  5. Check your other accounts on Have I Been Pwned. Your email address may appear in other breaches you don't know about yet.
  6. Monitor the apps you use going forward. Clearly watches the breach record for the companies behind your apps and alerts you the moment one appears.

Breach data from Have I Been Pwned. Listing here means the service appears in the public breach record — not that your personal data was affected.