Data breach
GeekedIn data breach
1,073,164 accounts · breached August 15, 2016
What happened
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.
What data leaked
- Email addresses
- Geographic locations
- Names
- Professional skills
- Usernames
- Years of professional experience
What to do if you had an account
- 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.
- 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.
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.