SaverSpy Data Breach (2018)
If you are a customer of SaverSpy, here’s what’s now in circulation.
In September 2018, security researcher Bob Diachenko discovered a massive collection of personal details exposed in an unprotected Mongo DB instance. The data appears to have been used in marketing campaigns (possibly for spam purposes) but had little identifying data about it other than a description of "Yahoo_090618_ SaverSpy". The data set provided to HIBP had almost 2.5M unique email addresses (all of which were from Yahoo!) alongside names, genders and physical addresses.
Assessing SaverSpy as a vendor?
Check your own domain — free, no cardEnter a work email. We count the addresses at that domain sitting in the leaked-data corpus, and how many arrived with a password.
Were you personally caught up in this? Run a free 15-second personal scan.
What the free scan actually returns
Found on people-search siteswe remove these
These listings are live, public, and legal to remove — and removing them is what we do.
Found in breach recordsverifiedreported — unverified
Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.
Leaked data cannot be deleted from the internet — anyone claiming otherwise is lying. Broker listings can be removed. We do the second, and show you exactly what to fix from the first.
For security and vendor-risk teams: a staff address in a leak does not mean you were breached — it usually means a third party was. We monitor a domain against 13.1B+ leaked records and tell you when one of your people appears. See what we would check →
Report details & sourcing
Related breaches
Dubsmash — 162 Million Accounts Sold in a Job Lot (2018)
The video-messaging app used PBKDF2, one of the better choices on this list. Its data still ended up…
MyFitnessPal — 144 Million Accounts, and Whether Yours Was Safe Depended on When You Joined (2018)
MyFitnessPal used SHA-1 for older accounts and bcrypt for newer ones. Whether your password survived…
Exactis — 340 Million Records of Profiling Data Nobody Consented To (2018)
A marketing data broker left an ElasticSearch node exposed with no firewall. It held about 340 milli…