Yam

yam.com

13,259,767
Exposed Records
Jun 2013
Breach Date
13 years ago
Unknown
Password Risk
News Media industry
News Media
Industry
Added to XposedOrNot on January 20, 2024 · #109 of 763 breaches by records exposed

About This Breach

Yam, a popular cryptocurrency platform, experienced a data breach in 2013 which resulted in the exposure of sensitive user data. The breach compromised key information such as email addresses, usernames, and hashed passwords, potentially posing a risk to the financial security of affected users.

Data Exposed

Usernames
Passwords
Email addresses
Names
Phone numbers

Breach Details

Breach Type Data Breach
Searchable Yes
Verified Yes
Sensitive Data No
Reference No reference available

Frequently Asked Questions

When did the Yam data breach happen?

Yam was breached in Jun 2013. The breach was added to the XposedOrNot index on January 20, 2024.

How many records were exposed in the Yam breach?

13,259,767 records were exposed, making it the #109 largest of the 763 breaches in our index.

What data was exposed in the Yam breach?

The exposed data includes: Usernames, Passwords, Email addresses, Names, Phone numbers.

What should I do if I was affected by the Yam breach?

Change your password on the affected service (and anywhere you reused it), turn on two-factor authentication, and set up free breach alerts on XposedOrNot so you know the moment your email appears in a new breach.

What Should You Do?

Urgent

Change Your Passwords

Update your password immediately, using 12+ characters with numbers and symbols.

High Priority

Enable Two-Factor Authentication

Add 2FA on all supported accounts using an authenticator app like Google Authenticator or Authy.

Recommended

Watch for Phishing Calls & SMS

Be cautious of unexpected calls or texts asking for personal information.

Recommended

Monitor Your Accounts

Set up login alerts and review account activity regularly for suspicious access.

Best Practice

Use a Password Manager

Never reuse passwords: use a password manager to generate unique ones for each account.