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

Recent Breaches › Youku Data Breach (2016)

CRITICAL severityConfirmedHow we verify

Youku Data Breach (2016): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·December 1, 2016

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

Youku Data Breach (2016)

Reported December 1, 2016. Approximately 91.9M people affected.

CRITICAL
Severity
91.9M
People affected
2
Data types exposed
December 1, 2016
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Youku Data Breach (2016) (reported December 1, 2016) exposed Email addresses and Passwords belonging to roughly 91.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 Youku Data Breach (2016) breach?
91.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.

In late 2016, the Chinese video streaming service Youku experienced a data breach that exposed 92 million unique user accounts. The incident, reported on December 1, 2016, affected 91.9 million people and involved email addresses paired with MD5 password hashes. The data later appeared in public breach repositories, including a contribution to Have I Been Pwned. The breach is notable because it involved a large volume of credential data from a major consumer platform. Public records do not detail the method of access or the exact timeline of the intrusion. No attribution to any specific actor has been confirmed in available reporting.

Inside the incident

The breach occurred sometime in late 2016. It resulted in the exposure of 92 million unique user accounts containing email addresses and corresponding MD5 password hashes. The dataset was later submitted to the Have I Been Pwned service by an individual using the handle rip@creep.im. No further technical details about the intrusion vector, duration, or internal systems affected have been disclosed in public sources.

How a breach like this happens

Incidents involving large volumes of user credentials often begin with unauthorized access to an organization’s database or application servers. Attackers may exploit vulnerabilities in web applications, obtain stolen administrative credentials, or leverage misconfigured storage systems. Once inside, they can copy tables that store account information. Passwords stored only as hashes, rather than in plain text, still carry risk if the hashing method is weak or if users have reused the same password elsewhere.

About Youku

Youku operates as a major online video streaming platform based in China. Services of this type maintain accounts for millions of users who upload, view, and share video content. Typical data held includes registration details such as email addresses and passwords, along with usage records. A compromise at this scale can affect a broad cross-section of users who rely on the platform for entertainment and communication.

What data was at risk

The breach is reported to have exposed email addresses and MD5 password hashes. Public summaries do not provide a complete inventory of every field that may have been taken. Organizations in the streaming sector commonly store additional profile information, payment details, or viewing history, yet the precise contents of the Youku dataset beyond the named fields remain unconfirmed.

The real-world impact

Exposed email addresses can be used for targeted phishing or sold on underground markets. MD5-hashed passwords increase the chance of account compromise if users have reused credentials on other sites, because older hashing methods can be processed more quickly by attackers. For the organization, the incident highlights the long-term consequences of storing large volumes of authentication data without additional protective measures such as stronger hashing or breach detection controls.

If your data was in this breach

Individuals can check whether their email address appears in known breach datasets by using a free exposure scan service. Practical next steps include changing the password on the affected account and any other services that share the same credentials. Enabling multi-factor authentication where available adds a further layer of protection against unauthorized access.

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

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

1 reported incident on record.

See Youku’s full breach history →

More recent breaches

Ethereum Data Breach (2016)December 16, 2016Anti Public Combo List Data Breach (2016)December 16, 2016PayAsUGym Data Breach (2016)December 15, 2016MrExcel Data Breach (2016)December 5, 2016

Latest breaches

Read GalaxyWarden’s full analysis of the Youku Data Breach (2016) →

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