Flash Flash Revolution (2016 breach) Data Breach (2016): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Flash Flash Revolution (2016 breach) Data Breach (2016) (reported February 1, 2016) exposed Email addresses, Passwords and Usernames belonging to roughly 1.8M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.
What happened
In February 2016, the music-based rhythm game Flash Flash Revolution was compromised, resulting in the exposure of 1.8 million accounts. The breach involved the site's vBulletin forum and led to the disclosure of email addresses, usernames, IP addresses, and salted MD5 password hashes. The incident was reported on 1 February 2016. No further details on the method of intrusion or the precise timeline of access have been disclosed in available records.
How a breach like this happens
Incidents affecting forum platforms often begin with the exploitation of known software vulnerabilities or weak authentication controls. Attackers may gain initial access through unpatched web applications, stolen administrative credentials, or misconfigured database permissions. Once inside, they can extract user tables that contain login details and associated metadata. In older forum systems, password data is sometimes stored in hashed form that can be processed offline if the hashing method is no longer considered strong by current standards.
Flash Flash Revolution (2016 breach) and its sector
Flash Flash Revolution operated as an online rhythm game that maintained a community forum for player interaction, score tracking, and discussion. Platforms of this type routinely collect usernames, email addresses, and IP addresses to manage accounts and moderate activity. The use of a vBulletin installation was common among independent gaming sites during that period. A breach at such a service is consequential because the data can be reused across other sites where users maintain similar credentials, extending the reach of the incident beyond the original platform.
What data was at risk
The records indicate that email addresses, usernames, IP addresses, and salted MD5 password hashes were exposed. No additional categories of information, such as payment details or private messages, are named in the available reporting. The exact scope of any further data that may have been accessed remains unconfirmed.
The real-world impact
Individuals whose information appeared in the incident face the possibility that their email addresses could be used for targeted phishing or that reused passwords could be tested on other services. Salted MD5 hashes require additional computational effort to attempt reversal, yet older hashing methods increase the chance that some passwords could eventually be recovered. For the organisation, the event highlighted the long-term maintenance burden of legacy forum software and the need to notify users promptly so they could take protective steps.
Were you affected?
Anyone who created an account on Flash Flash Revolution before February 2016 should assume their email address and username may have been included. Begin by changing the password on that account and on any other service where the same password was used. Enable multi-factor authentication where available. Readers can also run a free exposure scan of their email address against known breach data to check for appearances in this or other incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
Ethereum Data Breach (2016)Anti Public Combo List Data Breach (2016)PayAsUGym Data Breach (2016)MrExcel Data Breach (2016)Latest breaches
Read GalaxyWarden’s full analysis of the Flash Flash Revolution (2016 breach) Data Breach (2016) →
Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.
Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.
Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.