RuneScape Boards Data Breach (2011): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The RuneScape Boards Data Breach (2011) (reported December 26, 2011) exposed Email addresses, IP addresses, Passwords and Usernames belonging to roughly 223K 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
The breach affected the RuneScape Boards forum, a site that operated on the vBulletin platform. Records indicate that 223,000 unique email addresses were exposed, together with usernames, IP addresses, and salted MD5 password hashes. The compromise occurred around 2011, and the dataset was later included in larger compilations of historical breach material. No further technical details on the initial intrusion or the precise date of the event have been disclosed in available reports.
How a breach like this happens
Forum platforms from that period commonly stored user credentials in hashed form, with salts added to slow down automated cracking attempts. When an attacker gains access to the underlying database, whether through an unpatched vulnerability, weak administrative controls, or compromised hosting credentials, the entire set of account records can be copied. Once extracted, such data may circulate privately for years before appearing in public or semi-public archives. The redistribution of older datasets means that records from a single incident can surface repeatedly without any new compromise occurring.
Who is RuneScape Boards?
RuneScape Boards functioned as an online discussion space for players of the RuneScape game. Like many community forums of its era, it collected standard account information to manage user registrations and discussions. The service is now defunct, which limits opportunities for direct notification or further investigation by the original operators. Gaming-related forums typically retain contact details and login data for extended periods, making any exposure of those records relevant to former participants even after the site has closed.
What was likely exposed
The documented records include email addresses, usernames, IP addresses, and salted MD5 password hashes. These categories are confirmed in the available breach description. No additional data types, such as payment information or private messages, are named in the reported facts. Because the forum no longer operates, the exact scope of any other material that may have been present on the server at the time remains unconfirmed.
Why it matters
Email addresses paired with password hashes allow attackers to test whether the same credentials were reused on other services. IP addresses can reveal approximate locations at the time of account activity. Although the passwords were stored as salted hashes rather than plain text, older hashing methods can be processed offline if sufficient computing resources are applied. For individuals whose records appear in such datasets, the primary concern is continued reuse of credentials across sites rather than any immediate action by the original operators.
What to do if you're exposed
Review any accounts that still use the email address associated with the forum and change passwords where the same combination may have been reused. Enable multi-factor authentication on services that support it. Monitor incoming email for unusual login attempts or password-reset requests. Individuals can also run a free exposure scan of their email address against known breach collections to determine whether their information appears in additional datasets.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
17173 Data Breach (2011)Stratfor Data Breach (2011)China Software Developer Network Data Breach (2011)Zhenai.com Data Breach (2011)Latest breaches
Read GalaxyWarden’s full analysis of the RuneScape Boards Data Breach (2011) →
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.