Social Networking · Community

vBulletin Data Breach (2015)

A forum software maker.

Pilot record · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
Elevated
Third of five bands on the Breach Risk Index
Observed minimumAt least this much was seen. Read it as a floor · as of November 9, 2026
What this rating measures

The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.

It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.

Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →

Data sensitivity
Sensitive

Includes a date of birth with partial identity detail. A date of birth cannot be changed.

Circulating
518,966 email addresses
Field types
9 seen
Breach date
Nov 2015
Observed as of
2026-11-09
Catalogued by Have I Been Pwned
How it unfoldedAbout 2 months from breach to listing
  1. Breach
  2. 11 years laterListed in breach catalogues
  3. Observed · scored
What came out

What data was exposed

Date of BirthCannot be reissued
Security question and answerCredential
Email AddressContact
IP AddressDevice
Password (hashed)Credential
Messaging HandleSocial
Spoken LanguageDemographic
Website URL (homepage)Social
Activity History (website activity)Notable exposure
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material
What it enables

How this data can be used against you

Partial

Account access

Account material that is weakened or incomplete.

Not enabled

Identity

No usable identity package in what circulates.

Not enabled

Physical targeting

No usable location detail in what circulates.

Not enabled

Social engineering

Nothing in what circulates to build an approach on.

Not enabled

Financial

No usable financial detail in what circulates.

Not enabled

Coercion

Nothing in what circulates is sensitive enough for leverage.

Not enabled

Health

No medical detail in what circulates.

Not enabled

Crypto

Nothing in what circulates is tied to crypto assets.

Enabled: the set on its own is enough · Partial: part of what is needed, or weakened · Not enabled: nothing usable in what circulates
What you should do

Two key actions to take

Change your vBulletin password

Change it anywhere you reused it too, and turn on two-step sign-in.

Treat messages about vBulletin with care

Do not act on a call, email or text about this breach. Contact vBulletin using a number you already have.

Check it yourself

Check whether you were affected

Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

Talk to us about your exposure

If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.

Request a confidential call →
Full record · 9 sections

The full breach analysis

What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.

  • What happened
  • Recent developments
  • Reported and circulating
  • Data points exposed
  • Downstream risk
  • Principal risk advisory
  • Threat actor
  • Background
  • Data context
No sign-in · nothing is recorded
What happened

How this breach 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.

Recent developments

What has happened since the breach

The vBulletin dataset circulated publicly; treat as part of the standing exposure landscape.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Not yet researched
Observed by ObscureIQ

Circulating

Observed as of
2026-11-09
Breach date
Nov 2015
Volume
518,966 email addresses
Fields seen
9date of birth, email address, website URL (homepage), messaging handle, IP address, password (hashed), security question and answer, spoken language, activity history (website activity)

The score is built only on what is seen circulating.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeCirculating
Date of BirthLasts for yearsNoYes
Email AddressLasts for yearsNoYes
Website URL (homepage)Lasts for yearsNoYes
Messaging HandleLasts for yearsNoYes
IP AddressExpires fastNoYes
Password (hashed)Expires fastNoYes
Security question and answerLasts for yearsNoYes
Spoken LanguageLasts for yearsNoYes
Activity History (website activity)Lasts for yearsNoYes

Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.

Downstream risk

How attackers can use this data

Practical risk: credential reuse enables account takeover across services. Compounding risk rises where this data links to other breached or brokered records.

Principal risk advisory

Risks for executives and other high-profile people

A social-platform breach: profile and contact-graph data supports impersonation, enrichment and social engineering. For a high-profile principal the main risk is credible impersonation and enrichment of existing exposure.

Threat actor

Who is behind this breach

No threat actor has been publicly attributed.

Background

About the company

vBulletin is a forum software maker.

Data context

Why the company holds this data

vBulletin is a forum software maker. Services like this typically hold activity history, dates of birth, email addresses, IP addresses, messaging handle, passwords, security questions, language, website url through account registration and normal operations.

TechnologySoftware & SaaSPrivate company2015

About this record

No reported total is on record for this breach. The circulating figure, 518,966 email addresses, is what has been observed in the published data. Circulation was last verified on 2026-11-09. The score was last computed on 2026-11-09. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI