Digimon
MEDIUM RISKData breach — September 2016
In September 2016, over 16GB of logs from a service indicated to be digimon.co.in were obtained, most likely from an unprotected Mongo DB instance. The service ceased running shortly afterwards and no information remains about the precise nature of it. Based on enquiries made via Twitter, it appears to have been a mail service possibly based on PowerMTA and used for delivering spam. The logs contained information including 7.7M unique email recipients (names and addresses), mail server IP addresses, email subjects and tracking information including mail opens and clicks.
search Check if you were affected — freeData exposed in this breach
What happened in the Digimon data breach?
In September 2016, over 16GB of logs from a service indicated to be digimon.co.in were obtained, most likely from an unprotected Mongo DB instance. The service ceased running shortly afterwards and no information remains about the precise nature of it. Based on enquiries made via Twitter, it appears to have been a mail service possibly based on PowerMTA and used for delivering spam. The logs contained information including 7.7M unique email recipients (names and addresses), mail server IP addresses, email subjects and tracking information including mail opens and clicks.
The exposed data included 4 types of personal information. Learn more about what a data breach means for you.
Quick answer — was Digimon hacked?
Yes. Digimon was breached in September 2016. The breach exposed 7,687,679 records including email addresses, email messages, ip addresses. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.
Why was the Digimon breach so dangerous?
The Digimon breach exposed 7,687,679 records — that is 7.7M people whose personal data is now circulating on the dark web. The combination of email addresses, email messages, ip addresses makes this a medium-risk breach that should be addressed promptly.
Don't wait to find out — check if your email was exposed in this breach now.
What data was stolen in the Digimon breach?
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Email messages — used for phishing attacks and credential stuffing against your other accounts
IP addresses — combined with other data, used for identity theft and physical fraud
Names — used to build profiles and target you with personalised scams
Is the Digimon breach still dangerous in 2026?
Yes. Stolen data from the Digimon breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2016 are still actively used in credential stuffing attacks today.
Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your Digimon password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.
Frequently asked about the Digimon breach
Approximately 7,687,679 user records were exposed in the Digimon breach in September 2016.
Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your Digimon password elsewhere and haven't changed it, those accounts remain at risk today.
Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full Digimon dataset and tell you instantly whether your email was exposed and what data was taken.
Change your Digimon password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.
Who was affected by the Digimon breach?
The Digimon data breach affected approximately 7,687,679 users who had accounts with the service. While not the largest breach on record, it still represents a significant number of compromised accounts in our database of 970+ known breaches.
If you ever created an account with Digimon or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.
If your email was in the Digimon breach
Change your Digimon password immediately
Go to Digimon and change your password right now. Use a strong, unique password that you have never used anywhere else.
Change any account sharing that password
If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.
Enable two-factor authentication
Turn on 2FA on Digimon and every important account. Even if your password is known, attackers cannot get in without the second factor.
Check your other accounts for this breach
Run a full email check to see every breach your email appears in — not just this one.
searchCheck all my breaches — freeOther major breaches
Was my email hacked?
Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.
search Check my email now — it's freeNo signup required · Results in under 5 seconds · Your data is never stored