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

Recent Breaches › Zynga Data Breach (2019)

CRITICAL severityConfirmedHow we verify

Zynga Data Breach (2019): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·September 1, 2019

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

Zynga Data Breach (2019)

Reported September 1, 2019. Approximately 172.9M people affected.

CRITICAL
Severity
172.9M
People affected
4
Data types exposed
September 1, 2019
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Zynga Data Breach (2019) (reported September 1, 2019) exposed Email addresses, Passwords, Phone numbers and Usernames belonging to roughly 172.9M 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
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Zynga Data Breach (2019) breach?
172.9M 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.

People whose accounts were created with Zynga services may now face increased risk of targeted phishing, credential reuse on other sites, and unwanted contact through exposed phone numbers. The scale of the incident means these possibilities affect a large number of individuals who played the company's games. In September 2019, Zynga reported a data breach that affected 172.9 million people. The exposed records included email addresses, usernames, phone numbers, and passwords stored as salted SHA-1 hashes. The data set was later provided to Have I Been Pwned by dehashed.com.

Inside the incident

The breach was made public on 1 September 2019. Available records state that 172.9 million unique email addresses were involved, together with the associated usernames, phone numbers, and hashed passwords. No further information on the method of access, the exact date of the intrusion, or the duration of unauthorized activity has been disclosed in public reports.

How a breach like this happens

Incidents involving large user databases often begin with an attacker obtaining remote access to an application or server environment. Once inside, the actor can copy tables that store account credentials and contact details. Passwords are sometimes stored in hashed form, yet older hashing methods can still be processed offline if the attacker also obtains the salt values. The subsequent distribution of the data set through third-party sites is a common pattern after the initial extraction.

Zynga and its sector

Zynga develops and operates online games, including Words with Friends. Companies in this sector maintain accounts for millions of players and therefore collect the identifiers needed for login, account recovery, and in-game communication. A breach at one such firm can expose data that players have reused across other services, extending the practical impact beyond the original game platform.

What data was at risk

The records supplied to breach-tracking services list four categories of information. Public reporting does not confirm whether additional fields were present in the original data set.

Why it matters

Email addresses combined with usernames can facilitate targeted phishing campaigns that appear to originate from the gaming service. Phone numbers increase the chance of unsolicited messages or calls. Although the passwords were hashed, the use of SHA-1 means that any offline cracking effort faces fewer technical barriers than with stronger, modern algorithms. For the organization, the incident adds to the record of third-party disclosures that users and regulators may review when assessing data-handling practices.

If your data was in this breach

Change the password on any Zynga account and on any other service where the same password was used. Enable two-factor authentication where available and review recent login activity for signs of unauthorized 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 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

CompanyZynga security record
70/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See Zynga’s full breach history →

More recent breaches

Sonicbids Data Breach (2019)December 30, 2019Go Ninja Data Breach (2019)December 17, 2019GameSprite Data Breach (2019)December 17, 2019Avvo Data Breach (2019)December 17, 2019

Latest breaches

Read GalaxyWarden’s full analysis of the Zynga Data Breach (2019) →

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