What was exposed, when it happened, and which databases confirm it.
- accounts
- 845,012
- Breached
- August 30, 2016
- Last Update
- March 25, 2018
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.
What happened
In August 2016, the Swiss scholarly open access publisher known as MDPI had 17.5GB of data obtained from an unprotected Mongo DB instance. The data contained email exchanges between MDPI and their authors and reviewers which included 845k unique email addresses. MDPI have confirmed that the system has since been protected and that no data of a sensitive nature was impacted. As such, they concluded that notification to their subscribers was not necessary due to the fact that all their authors and reviewers are available online on their website.
Compromised Info
- Email addresses
- Email messages
- IP addresses
- Names
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- HIBP
FAQ
What was leaked in the MDPI breach?
The MDPI breach exposed: Email addresses, Email messages, IP addresses, and Names.
When did the MDPI breach happen?
The MDPI breach was disclosed on August 30, 2016 and affected 845,012 records.
Am I affected by the MDPI breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the MDPI leak.