MyFitnessPal — 144 Million Accounts, and Whether Yours Was Safe Depended on When You Joined (2018)
If you have an account with MyFitnessPal, here’s what’s now in circulation.
MyFitnessPal used SHA-1 for older accounts and bcrypt for newer ones. Whether your password survived depends entirely on your signup date — and nobody tells you which side of that line you were on.
What happened
In February 2018 the diet and exercise service MyFitnessPal was breached, exposing 143,606,147 unique email addresses alongside usernames and IP addresses. In 2019 the data was listed for sale on a dark-web marketplace among the GnosticPlayers batches and subsequently circulated widely.
Two different breaches wearing one name
The password storage is the unusual part and it is genuinely important. MyFitnessPal stored passwords as SHA-1 for earlier accounts and bcrypt for newer ones. The company had migrated its hashing at some point, and the breach caught it mid-transition.
The practical consequence is that this single breach has two completely different risk profiles. If your account predates the migration, your password was protected by a fast hash and should be considered recoverable. If it postdates it, bcrypt almost certainly held.
And here is the part no advice column will tell you: you have no way to find out which group you are in. The migration date was never published, your signup date is not something most people remember, and the dataset does not annotate it. The only safe assumption is the pessimistic one — that yours was SHA-1.
This is exactly the failure mode of a generated breach page that reads DataClasses: Passwords and prints one sentence. The catalogue field is identical for MyFitnessPal and for Wattpad. The correct advice is not.
What a fitness account reveals
The breach itself did not expose weight logs, food diaries or workout history — the exposed classes are email addresses, usernames, IP addresses and passwords. It is worth being precise about that, because inflated claims about health data circulate around this incident.
What the dataset does establish is membership: confirmation that a given person used a weight-management service. That inference alone has been enough to fuel targeted advertising and, in some documented patterns, extortion-flavoured phishing. IP addresses add rough location at the time of use.
The identity-chain implication
Health and fitness accounts are almost always registered with a person's primary personal email address, not a throwaway. People compartmentalise gaming and shopping; they rarely compartmentalise the app they weigh in on.
That makes a fitness-service dataset a high-confidence map from a real, actively used address to a real person — which is precisely the anchor an attacker needs before spending effort on anything else. Under Armour owned MyFitnessPal at the time, and the corporate parent has its own separate entry in the catalogue; the two are distinct incidents and should not be conflated.
What to do now
What You Should Do
- Assume SHA-1 unless you know you joined late — you cannot determine which hash protected your account, so plan for the worse one
- Change every reuse of that password first; the MyFitnessPal account itself is the least valuable thing at risk
- Check the same address against Dubsmash, MyHeritage and Canva, which were sold in the same 2019 batches
- Treat emails referencing weight, diet or fitness goals as pretexts built on membership inference, not on leaked health data
- Enable 2FA on the email address used, since fitness signups are usually a primary personal address
What the free scan actually returns
Found on people-search siteswe remove these
These listings are live, public, and legal to remove. That’s what a Deep Sweep buys.
Found in breach recordsverifiedreported — unverified
Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.
Leaked data cannot be deleted from the internet — anyone claiming otherwise is lying. Broker listings can be removed. We do the second, and show you exactly what to fix from the first.
Report details & sourcing
Related breaches
MySpace — 360 Million Accounts, and the Weakest Password Storage of Any Major Breach (2008)
MySpace stored the SHA-1 hash of only the first ten characters of your password, lowercased, with no…
Zynga — 173 Million Words With Friends Accounts (2019)
The maker of Words With Friends lost 173 million accounts with salted SHA-1 passwords and, unusually…
LinkedIn — 164 Million Accounts, Unsalted SHA-1, Four Years in the Dark (2012)
Hacked in 2012, sold in 2016. LinkedIn stored passwords as unsalted SHA-1 and the vast majority were…