Digimon data breach
The Digimon breach happened on September 5, 2016 and exposed 7,687,679 accounts. 4 kinds of data were exposed.
Overview
- Site
- digimon.co.in
- Breach date
- September 5, 2016
- Recorded on
- September 28, 2018
- Accounts exposed
- 7,687,679
- Exposed data
- Email addresses, Email messages, IP addresses, Names
- Risk score
- 45 out of 100
This data is a list collected for sending spam, not a breach of the service itself.
Risk based on the exposed data
This breach scores 45 out of 100. The score is driven mostly by Email messages, Email addresses, Names.
The risk score is a guide to how dangerous a breach is, judged by the kinds of data exposed. The number of accounts is not included.
Breaches from the same period
- uuu9 (2016-09-06, 7,485,802 accounts)
- NemoWeb (2016-09-04, 3,472,916 accounts)
- ClixSense (2016-09-04, 2,424,784 accounts)
What affected users should do
- Passwords were not exposed, but you may receive fake emails aimed at the exposed email addresses.
- Turn on two-factor authentication for your login.
This site organizes publicly available information about data breaches. Data as of September 28, 2018. Breach dates are as originally listed; when only the month is known, the date is recorded as the 1st.