Back to Blog
critical severity September 01, 2019 · 3 min read

Zynga — 173 Million Words With Friends Accounts (2019)

If you have an account with Zynga, here’s what’s now in circulation.

The maker of Words With Friends lost 173 million accounts with salted SHA-1 passwords and, unusually for a casual-gaming breach, phone numbers. Words With Friends skews older and skews family, which changes who is exposed.

A word-game tile rack over a leaked account record

What happened

In September 2019 the game developer Zynga — best known for Words With Friends and FarmVille — suffered a breach exposing 172,869,660 unique email addresses alongside usernames, phone numbers and passwords stored as salted SHA-1 hashes. The data was provided to Have I Been Pwned by dehashed.com. Reporting at the time carried a considerably larger claim from the seller; the 173 million figure is the count of unique addresses actually verified in the data.

Caught in this breach?
You can’t unleak a breach. You can take away what it’s worth.
Deep Sweep shows you every leak tied to you and exactly what to change. Then it strips your name, address and family off the look-up sites that turn a leaked record into somebody knocking on your door — $29 one-time, includes 30 days of Protection. We write to 582 companies. No subscription to start.
Scan free, then Deep Sweep — $29 →
Not ready yet? Run a free breach check on this email
We’ll check it against 13.1B+ leaked records right now — no account needed. Continuous monitoring & alerts are part of Protection.

Salted SHA-1 is better than MySpace and still not good

Zynga salted its hashes, which is the difference between this breach and the MySpace one. A salt means every account gets a unique hash even when two people chose the same password, so an attacker cannot crack the whole set at once. That genuinely helps.

What a salt does not fix is speed. SHA-1 is designed to be fast, which is a virtue in a checksum and a liability in a password hash — modern hardware tries enormous numbers of candidates per second against a single salted hash. The result is predictable: weak and moderate passwords fall, strong ones mostly hold. If your Zynga password was a common word with a number after it, treat it as recovered. If it was long and random, it probably survived.

This is why blanket advice fails. The same sentence — "passwords were exposed" — describes MySpace, where nothing survived, and Wattpad, where essentially everything did.

Why the phone numbers are the surprise

Casual games do not usually hold phone numbers. Zynga's did, and that single field changes the character of the breach: an email address plus a phone number plus a username is enough to pivot into SIM-swap and account-recovery attacks against services far more valuable than a word game.

There is a demographic point here that generic coverage misses. Words With Friends has an unusually old and unusually family-connected player base — it is the game people play with their parents and grandparents. A breach of a shooter exposes gamers; a breach of Words With Friends exposes the least security-hardened members of a family, using an email address they have had for twenty years and a password they use everywhere.

The identity-chain implication

Gaming handles are one of the most reliable joins in the whole identity graph, because people keep them. A username chosen for a Zynga account in 2012 very often still appears on Steam, Discord and Reddit, and each of those carries different fragments of the same person.

Here the join is unusually rich: the dataset supplies handle, email address and phone number in one row, so it collapses three separate discovery steps into one lookup.

What to do now

What You Should Do

  1. Change the password if it was anything guessable — salted SHA-1 protects strong passwords and loses weak ones
  2. Check whether the Zynga username is a handle you still use publicly; if so, it links this record to your current accounts
  3. Set a carrier port-out PIN, because this breach paired your phone number with your email address
  4. Check older relatives who play Words With Friends — this dataset disproportionately covers people who reuse one password everywhere
  5. Enable 2FA on the email account used to register, since that is the recovery path for everything else

What the free scan actually returns

Sample resultyou@email.comIllustrative — not a real person

Found on people-search siteswe remove these

These listings are live, public, and legal to remove. That’s what a Deep Sweep buys.

value redacted in this sampleage, relatives, address historySpokeo
value redacted in this samplephone, household, property recordsBeenVerified
value redacted in this sample582 companies checked

Found in breach recordsverifiedreported — unverified

Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.

verifiedvalue redacted in this samplepassword + phone · 2024telecom breach
unverifiedvalue redacted in this sampleclaimed in ransomware listing · 2026leak-site claim

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.

Were you a Zynga customer?
Zynga is one breach. Your email is probably in others.
172.9M email addresses accounts were exposed here. Check whether yours is one — and find every other leak tied to the same address, in about 15 seconds. No account, 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.

Report details & sourcing

Severity Critical
Disclosed September 01, 2019
Last reviewed July 22, 2026
Affected 172.9M email addresses
Data exposed Email addressesUsernamesPasswordsPhone numbers
Editorial & sourcing policy
GalaxyWarden is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data. Breach information is compiled from publicly accessible sources and threat-intelligence platforms, and is reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — see our content & takedown policy or write to support@galaxywarden.com.
Share this Post on X Reddit Email