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

Recent Breaches › Yam Data Breach (2013)

CRITICAL severityConfirmedHow we verify

Yam Data Breach (2013): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·June 2, 2013

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

Yam Data Breach (2013)

Reported June 2, 2013. Approximately 13.3M people affected.

CRITICAL
Severity
13.3M
People affected
7
Data types exposed
June 2, 2013
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Yam Data Breach (2013) (reported June 2, 2013) exposed Dates of birth, Email addresses, Names and Passwords belonging to roughly 13.3M 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 Yam Data Breach (2013) breach?
13.3M 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 June 2013 the Taiwanese website Yam.com experienced a data breach that exposed records belonging to 13.3 million users. The incident itself received limited public attention at the time; the dataset later appeared on a hacking forum in 2021, where it was described as containing email addresses, names, usernames, phone numbers, physical addresses, dates of birth and unsalted MD5 password hashes.

The breach is notable because of the volume of personal identifiers involved and the age of the compromised credentials, which remain usable for account takeover attempts years later.

What happened

The breach occurred in June 2013 at Yam.com, a Taiwanese online service. Public reporting at the time did not detail the method of intrusion or the exact number of records taken. In 2021 the dataset resurfaced on a popular hacking forum, where the contents were listed as 13 million unique email addresses together with the additional fields noted above. No official statement from the organisation regarding the scale or cause of the incident has been referenced in available records.

How a breach like this happens

Incidents involving large volumes of user account data commonly begin with an attacker obtaining access to an organisation’s database server. This can occur through exploitation of unpatched software, compromised administrative credentials, or misconfigured access controls that leave databases reachable from the public internet. Once inside, an attacker can copy tables containing user profiles and authentication data. Passwords stored as unsalted hashes are especially exposed because they can be processed offline with modern hardware to recover the original values.

Who is Yam?

Yam.com operated as a Taiwanese web portal and social platform that required users to create accounts. Services of this type routinely collect names, contact details, dates of birth and physical addresses to support registration, messaging and location-based features. A breach at such a site therefore places at risk the personal contact information and login credentials of a broad segment of the platform’s user base.

What was likely exposed

The 2021 forum posting listed the following data elements as present in the dataset:

Contemporary reports did not confirm whether additional fields such as payment information were included. The precise contents of the original breach therefore remain limited to the fields described in the later disclosure.

The real-world impact

Individuals whose records appear in the dataset face an elevated risk that their email addresses and recovered passwords will be used in credential-stuffing attacks against other online services. Phone numbers and physical addresses can facilitate targeted phishing or unwanted contact. For the organisation, the incident illustrates the long-term consequences of storing authentication data without modern hashing practices, as unsalted MD5 values remain susceptible to reversal long after the original compromise.

If your data was in this breach

Change passwords on any accounts that reuse the Yam.com credentials, beginning with high-value services such as email and banking. Enable multi-factor authentication wherever available. Monitor incoming email and phone communications for signs of targeted phishing that reference the exposed personal details. Readers can run a free exposure scan of their email address against known breach data to determine whether their information appears in this or other published datasets.

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

CompanyYam security record
73/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See Yam’s full breach history →

More recent breaches

Astropid Data Breach (2013)December 19, 2013Torrent Invites Data Breach (2013)December 12, 2013Pixel Federation Data Breach (2013)December 4, 2013Vodafone Data Breach (2013)November 30, 2013

Latest breaches

Read GalaxyWarden’s full analysis of the Yam Data Breach (2013) →

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