GeekedIn Data Breach (2016)
GeekedIn (geekedin.net) had a breach on or around Aug 15, 2016 that exposed 1,073,164 accounts. It was added to Have I Been Pwned on Nov 17, 2016.
What Was Exposed
- Email addresses
- Geographic locations
- Names
- Professional skills
- Usernames
- Years of professional experience
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.
Description: Have I Been Pwned, CC BY 4.0
Was My Account Included?
Enter your email address at haveibeenpwned.com to see whether it appears in this or other breaches. We don't ask for your email on this site.
What to Do Now
If Your Email Address Was Exposed
- Expect more phishing: messages that mention the company in the breach are a common trick.
- Don't click links in unexpected "security alert" emails; go to the website directly.
- You can check which known breaches include your email at haveibeenpwned.com.
What to Do Now
- Read the notice letter carefully: it should say what was exposed, when, and what the organization is offering (often free credit monitoring).
- If anything sensitive was involved, a free credit freeze with Equifax, Experian and TransUnion is the strongest single step.
- Watch for phishing that mentions the breach. Contact the organization only through phone numbers or websites you find yourself.
- Keep the letter: you may need it for a claim, a settlement or a dispute later.