Lumin PDF data breach

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.

What data leaked

• Auth tokens
• Email addresses
• Genders
• Names
• Passwords
• Spoken languages
• Usernames

What to do if you had an account

1. Change the password. Change your password on this service. If you used the same password anywhere else, change it there too: attackers try leaked email and password pairs on other sites automatically. A password manager makes one unique password per site practical.
2. Turn on two-step sign-in. Enable two-factor authentication where the service offers it, preferably with an authenticator app or a passkey. A leaked password alone is then not enough to get in.
3. Expect targeted phishing. Leaked contact details are used to write convincing fake messages that mention the breached company or your real name. Do not click links in unexpected emails or texts about this account; go to the site by typing its address.
4. Sign out everywhere. Use the service's 'sign out of all devices' option so that stolen session tokens stop working, then sign in again.

Check your email at haveibeenpwned.com

We do not run email lookups ourselves. The search is done on haveibeenpwned.com, the service this list comes from.