Glofox Data Breach (2020): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Glofox Data Breach (2020) (reported March 27, 2020) exposed Dates of birth, Email addresses, Genders and Names belonging to roughly 2.3M 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.
Inside the incident
Public records state that the breach affected 2.3 million membership records held by Glofox. The data types confirmed as exposed are dates of birth, email addresses, genders, names, phone numbers and passwords stored as unsalted MD5 hashes. No further details on the timing of access, the method of intrusion or the precise volume of records accessed beyond the reported total have been disclosed in available reporting.
How a breach like this happens
Incidents involving the exposure of customer records from service providers often begin with unauthorised access to internal systems or third-party connections. Attackers may exploit unpatched software, weak authentication controls or misconfigured storage to reach databases that contain user information. Once inside, data can be copied and later posted or sold. In many cases the exact entry point remains undisclosed by the affected organisation or investigators.
Who is Glofox?
Glofox supplies software used by fitness centres and gyms to manage memberships, class bookings and member communications. Companies in this sector routinely store personal details supplied during sign-up so that operators can contact members, verify identities and process renewals. A breach at such a provider therefore touches records belonging to individuals who may not have had a direct relationship with Glofox itself.
What was likely exposed
The breach record lists the following data elements as exposed: dates of birth, email addresses, genders, names, phone numbers and passwords stored as unsalted MD5 hashes. No additional categories of information have been confirmed. Organisations of this type commonly hold further details such as payment information or attendance histories, yet the exact contents of the 2.3 million records remain limited to the fields already named.
Why it matters
Names, email addresses and phone numbers can be used for targeted phishing or unwanted contact. Dates of birth and genders add to the profile that can be assembled about an individual. Passwords stored as unsalted MD5 hashes are comparatively weak; if reused elsewhere they may be recovered more easily than passwords protected by stronger methods. For the organisation, the incident creates legal, regulatory and operational obligations around notification and remediation.
What to do if you're exposed
Individuals can change passwords on any account that reuses the exposed credentials and enable multi-factor authentication where available. Monitoring email and phone accounts for unusual activity is advisable. Readers can run a free exposure scan of their email address against known breach data sets to check whether their information appears 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
MEO Data Breach (2020)NetGalley Data Breach (2020)MMG Fusion Data Breach (2020)DriveSure Data Breach (2020)Latest breaches
Read GalaxyWarden’s full analysis of the Glofox Data Breach (2020) →
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.