Tigo

tigo.chat

2,787,240
Exposed Records
Mar 2023
Breach Date
3 years ago
Hard to Crack
Password Risk
Information Technology industry
Information Technology
Industry
Added to XposedOrNot on July 14, 2025 · #261 of 763 breaches by records exposed

About This Breach

The Tigo Data Breach in mid-2023 involved the exposure of 300GB of data from the Chinese video chat platform, containing over 100 million records. The breach included more than 700K unique names, usernames, email and IP addresses, genders, profile photos, and private messages.

Data Exposed

Email addresses
Usernames
Passwords
Names
Physical addresses
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 Tigo data breach happen?

Tigo was breached in Mar 2023. The breach was added to the XposedOrNot index on July 14, 2025.

How many records were exposed in the Tigo breach?

2,787,240 records were exposed, making it the #261 largest of the 763 breaches in our index.

What data was exposed in the Tigo breach?

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

What should I do if I was affected by the Tigo 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

Beware of Scam Mail

Be skeptical of unexpected correspondence requesting personal details.

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.