All Breaches
June 21, 2022 Unverified Social Media

Yippi Alleged Data Exposure

The 2022 Yippi Web data breach occurred in June 2022 when backend MySQL databases belonging to Yippi (yippiweb.com / TOGA Limited), a popular Southeast Asian social messaging and lifestyle super-app, were published on BreachForums.

26.6 Thousand
Email Identifiers
6
Data Types
Medium
Exposure Scope
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

6
  • Email addresses
  • Passwords
  • Usernames
  • Phone numbers
  • Geographic locations
  • IP addresses

About This Record

What data was exposed in the Yippi incident?

The leaked SQL dump (yippiweb.sql) comprises core user identity tables (tc_user) alongside Openfire XMPP communication server logs. Compromised data classes include:

  • Identity & Account Data: Usernames, nicknames, internal UIDs, and profile photo avatar links.
  • Contact Coordinates: User email addresses and international phone numbers.
  • Authentication Secrets: MD5-hashed account passwords.
  • Geographic & Network Metadata: Registered province/city coordinates and historical client IP addresses.

How many accounts were affected?

Standardized RFC 5322 ASCII verification confirmed 26,569 unique valid email addresses across the database. The broader user table contains over 570,000 profile records, primarily registered via mobile phone numbers.

Security analysis and guidance

Unsalted or poorly protected MD5 password hashes are vulnerable to rapid rainbow-table lookups and brute-force cracking. The exposure of paired mobile numbers and emails elevates risks of targeted smishing and account takeover. Affected users should:

  • Change passwords across Yippi and any services where identical credentials were reused.
  • Enable two-factor authentication (2FA) wherever supported.
  • Exercise heightened caution against unexpected SMS verification codes or password reset prompts.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information