LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › CrackingForum Data Breach (2016)

HIGH severityConfirmedHow we verify

CrackingForum Data Breach (2016): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·July 1, 2016

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

CrackingForum Data Breach (2016)

Reported July 1, 2016. Approximately 660K people affected.

HIGH
Severity
660K
People affected
4
Data types exposed
July 1, 2016
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The CrackingForum Data Breach (2016) (reported July 1, 2016) exposed Email addresses, IP addresses, Passwords and Usernames belonging to roughly 660K 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.

Severity & verification
HIGH severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the CrackingForum Data Breach (2016) breach?
660K accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

In mid-2016, the online forum CrackingForum experienced a data breach that exposed information belonging to approximately 660,000 users. The incident came to light when it was reported on July 1, 2016. Details indicate that the forum, which operated on the vBulletin platform, had email addresses, IP addresses, usernames, and salted MD5 password hashes compromised. This event illustrates the ongoing exposure risks faced by niche online communities whose members often maintain accounts across multiple platforms.

Inside the incident

The breach affected 660,000 user records on the CrackingForum site. The exposed data included email addresses, IP addresses, usernames, and salted MD5 hashes. The forum ran on vBulletin software at the time. No further technical details on the method of access or the exact date range of the intrusion have been disclosed in available reports.

How a breach like this happens

Web forums built on older platforms can become targets when software updates are not applied promptly or when authentication mechanisms remain unchanged over time. Attackers may exploit known vulnerabilities in forum software or obtain credentials through unrelated compromises elsewhere. Once inside, they can extract user tables that contain both identifiers and password hashes, which are then shared or sold in underground channels.

About CrackingForum

CrackingForum operated as an online discussion board focused on topics related to software modification and circumvention techniques. Such forums typically require user registration and store account details to manage access and discussions. A breach at a site of this nature is consequential because participants frequently reuse usernames or passwords on other services, and the presence of IP addresses can link online activity to specific network locations.

The information in question

The records confirmed as exposed consist of email addresses, IP addresses, usernames, and salted MD5 hashes. The exact contents of any additional fields remain unconfirmed. Organisations that run discussion forums commonly retain these categories of data to support account creation, login functions, and moderation, though the presence or absence of further information in this specific case has not been publicly detailed.

The real-world impact

Individuals whose records appeared in the dataset face the possibility that their email addresses and password hashes could be tested against other online accounts. IP addresses may allow correlation of forum activity with other online behaviour. For the organisation, the incident highlights the long-term storage of user credentials in a format that, while hashed, can still be processed offline by actors with sufficient resources.

What to do if you're exposed

Review any accounts that share the same email address or username and change passwords where reuse is suspected. Enable multi-factor authentication on services that support it. Monitor login notifications and consider using a password manager to generate and store unique credentials. Readers can 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.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyCrackingForum security record
73/100
DoxxScan™ · Moderate doxx risk
B- 78Above-average record

1 reported incident on record.

See CrackingForum’s full breach history →

More recent breaches

Anti Public Combo List Data Breach (2016)December 16, 2016Ethereum Data Breach (2016)December 16, 2016PayAsUGym Data Breach (2016)December 15, 2016MrExcel Data Breach (2016)December 5, 2016

Latest breaches

Read GalaxyWarden’s full analysis of the CrackingForum 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.

ShareXLinkedInFacebookRedditWhatsAppTelegram