GeekedIn
What was exposed
Email addressesGeographic locationsNamesProfessional skillsUsernamesYears of professional experience
What to do if you were affected
- Expect more phishing and spam at this address. Treat messages that reference this company with extra caution.
- Be wary of targeted scams that use your personal details to sound convincing.
Details
In August 2016, the technology recruitment site GeekedIn left a MongoDB database exposed and over 8M records were extracted by an unknown third party. The breached data was originally scraped from GitHub in violation of their terms of use and contained information exposed in public profiles, including over 1 million members' email addresses. Full details on the incident (including how impacted members can see their leaked data) are covered in the blog post on 8 million GitHub profiles were leaked from GeekedIn's MongoDB - here's how to see yours .
Frequently asked questions
What is the GeekedIn data breach?
In August 2016, the technology recruitment site GeekedIn left a MongoDB database exposed and over 8M records were extracted by an unknown third party. The breached data was originally scraped from GitHub in violation of their terms of use and contained...
When did the data breach happen?
This data breach occurred around August 2016.
How many accounts were affected?
Around 1,073,164 accounts were affected.
What information was exposed?
Exposed data included Email addresses, Geographic locations, Names, Professional skills, Usernames and Years of professional experience.
What should I do if I was affected?
Expect more phishing and spam at this address. Treat messages that reference this company with extra caution. Be wary of targeted scams that use your personal details to sound convincing.
Related breaches