MyFitnessPal Data Breach (2018): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The MyFitnessPal Data Breach (2018) (reported February 1, 2018) exposed Email addresses, IP addresses, Passwords and Usernames belonging to roughly 143.6M 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
The breach was publicly reported on 1 February 2018. Company statements at the time indicated that usernames, email addresses, IP addresses, and passwords hashed with SHA-1 for older accounts and bcrypt for newer accounts had been accessed. No further technical details about the intrusion method or the precise volume of records were released in the initial disclosure. In 2019 the same data set was listed for sale on a dark web marketplace alongside other large breach collections and subsequently appeared in broader circulation.
How a breach like this happens
Incidents involving bulk extraction of user account data often begin with an attacker obtaining access to an application server or database through a remote vulnerability, stolen administrative credentials, or misconfigured storage. Once inside, the attacker can copy tables containing user records. Passwords are frequently stored as hashes rather than plain text, yet the hashes themselves remain useful to attackers who can attempt offline cracking or reuse them in credential-stuffing attacks against other sites. The time between initial access and public discovery can range from weeks to years, and the data may change hands multiple times before appearing on marketplaces.
MyFitnessPal and its sector
MyFitnessPal operates a diet and exercise tracking platform that requires users to create accounts to log meals, workouts, and personal metrics. Services in this sector routinely collect email addresses for account management, IP addresses for security logging, and passwords for authentication. Because users often reuse credentials across multiple platforms, a compromise at one fitness application can supply attackers with material that is tested against email providers, banks, and workplace systems.
What was likely exposed
The reported data types are limited to four categories. Exact contents of the data set remain unconfirmed beyond the initial disclosure.
- Email addresses
- Usernames
- IP addresses
- Passwords stored as SHA-1 and bcrypt hashes
Why it matters
Email addresses combined with usernames allow attackers to map individuals across services and to craft targeted phishing messages. Hashed passwords can be subjected to cracking attempts, particularly the SHA-1 hashes associated with older accounts. IP addresses may reveal approximate locations at the time of account creation or last login. For the organisation, the incident created operational costs for notification, password resets, and security improvements, while also exposing the limits of its prior password-storage practices.
If your data was in this breach
Change the password on any MyFitnessPal account and on any other service where the same password was used. Enable multi-factor authentication wherever available. Review recent account activity for signs of unauthorised access. Readers can run a free exposure scan of their email address against known breach data sets to determine whether their information appears in this or other publicly documented incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
IIMJobs Data Breach (2018)BannerBit Data Breach (2018)BlankMediaGames Data Breach (2018)OGUsers (2019 breach) Data Breach (2018)Latest breaches
Read GalaxyWarden’s full analysis of the MyFitnessPal Data Breach (2018) →
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.