vBulletin Data Breach (2015)
A forum software maker.
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 →
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
Breach11 years laterListed in breach cataloguesObserved · scored
What data was exposed
How this data can be used against you
Account access
Account material that is weakened or incomplete.
Identity
No usable identity package in what circulates.
Physical targeting
No usable location detail in what circulates.
Social engineering
Nothing in what circulates to build an approach on.
Financial
No usable financial detail in what circulates.
Coercion
Nothing in what circulates is sensitive enough for leverage.
Health
No medical detail in what circulates.
Crypto
Nothing in what circulates is tied to crypto assets.
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 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.
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 →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
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.
What has happened since the breach
The vBulletin dataset circulated publicly; treat as part of the standing exposure landscape.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
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.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Circulating |
|---|---|---|---|
| Date of Birth | Lasts for years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| Website URL (homepage) | Lasts for years | No | Yes |
| Messaging Handle | Lasts for years | No | Yes |
| IP Address | Expires fast | No | Yes |
| Password (hashed) | Expires fast | No | Yes |
| Security question and answer | Lasts for years | No | Yes |
| Spoken Language | Lasts for years | No | Yes |
| Activity History (website activity) | Lasts for years | No | Yes |
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.
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.
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.
Who is behind this breach
No threat actor has been publicly attributed.
About the company
vBulletin is a forum software maker.
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.
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.