What was exposed, when it happened, and which databases confirm it.
- accounts
- 29,938,298
- Breached
- April 1, 2019
- Last Update
- September 18, 2019
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
What happened
In April 2019, the PDF management service Lumin PDF suffered a data breach. The breach wasn't publicly disclosed until September when 15.5M records of user data appeared for download on a popular hacking forum. The data had been left publicly exposed in a MongoDB instance after which Lumin PDF was allegedly been "contacted multiple times, but ignored all the queries". The exposed data included names, email addresses, genders, spoken language and either a bcrypt password hash or Google auth token. The data was provided to HIBP by a source who requested it be attributed to "[email protected]".
Compromised Info
- Auth tokens
- Email addresses
- Genders
- Names
- Passwords
- Spoken languages
- Usernames
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
- LeakCheck— linked via automatic string matching
- Dehashed— linked via domain matching
- HIBP
FAQ
What was leaked in the LuminPDF breach?
The LuminPDF breach exposed: Auth tokens, Email addresses, Genders, Names, Passwords, Spoken languages, and Usernames.
When did the LuminPDF breach happen?
The LuminPDF breach was disclosed on April 1, 2019 and affected 29,938,298 records.
Am I affected by the LuminPDF breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the LuminPDF leak.