Cross Fire Data Breach (2016)
Chinese first-person shooter game community.
Could reach Guarded if more of this data surfaces.
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.
- Volume
- Count not yet verified
- Field types
- 5 listed
- Breach date
- 2016-08-08
- Listed as of
- 2024-12-01
- Vector
- Web Application Exploit
8 years laterBreachListed in breach catalogues · 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 Cross Fire password
Change it anywhere you reused it too, and turn on two-step sign-in.
Treat messages about Cross Fire with care
Do not act on a call, email or text about this breach. Contact Cross Fire 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 August 2016, the Russian CrossFire gaming community forum (cfire.mail.ru) was hacked as part of a wave of attacks on mail.ru-hosted vBulletin gaming forums (~27 million accounts total across cfire, parap, and tanks). Attackers exploited SQL-injection flaws in the vBulletin Forumrunner add-on on outdated versions. Exposed data included usernames, email addresses, salted MD5 passwords, IP addresses, and dates of birth (~7.7M unique emails for CrossFire). (Note: this is the Russian mail.ru community forum for CrossFire, not a Chinese platform as previously tagged.)
What has happened since the breach
In August 2016, cfire.mail.ru was breached as part of a wave of attacks on mail.ru-hosted vBulletin gaming forums (also hitting parap.mail.ru and tanks.mail.ru; ~27 million accounts total). Attackers exploited SQL-injection vulnerabilities in the vBulletin "Forumrunner" add-on on outdated installations.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Listed in breach catalogues
- Listed as of
- 2024-12-01
- Breach date
- 2016-08-08
- Volume
- Count not yet verified
- Fields listed
- 5date of birth, email address, IP address, password (salted MD5 hash), username
The score is built only on what is listed in circulation.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Listed |
|---|---|---|---|
| Date of Birth | Lasts for years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| IP Address | Expires fast | No | Yes |
| Password (salted MD5 hash) | Fades over a few years | No | Yes |
| Username | 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
Exposure enables account takeover, fraud, phishing, and harassment. Competitive-game and purchase data can also support item theft and cross-platform targeting.
Risks for executives and other high-profile people
A consumer-service breach: contact and account data supports phishing, account takeover and profile enrichment. 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
Cross Fire (cfire.mail.ru) is the Russian community forum for the popular FPS game CrossFire, hosted on the mail.ru platform. It maintained player forum accounts.
Why the company holds this data
Online shooter platforms collect player accounts, emails, purchase history, gameplay activity, device data, and community interactions across live-service gaming workflows.
About this record
No reported total is on record for this breach. No count has been verified for this breach yet. Figures in older breach catalogues are not shown until they are checked against the data. The provisional score was computed on 2024-12-01 from the catalogue field list; it will be recomputed once the list is audited. 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.