GeekedIn
MEDIUM RISKData breach — August 2016
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.
search Check if you were affected — freeData exposed in this breach
What happened in 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 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.
The exposed data included 6 types of personal information. Learn more about what a data breach means for you.
Quick answer — was GeekedIn hacked?
Yes. GeekedIn was breached in August 2016. The breach exposed 1,073,164 records including email addresses, geographic locations, names. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.
Why was the GeekedIn breach so dangerous?
The GeekedIn breach exposed 1,073,164 records — that is 1.1M people whose personal data is now circulating on the dark web. The combination of email addresses, geographic locations, names makes this a medium-risk breach that should be addressed promptly.
Don't wait to find out — check if your email was exposed in this breach now.
What data was stolen in the GeekedIn breach?
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Geographic locations — may be combined with other breach data to build a profile for targeted attacks
Names — used to build profiles and target you with personalised scams
Professional skills — may be combined with other breach data to build a profile for targeted attacks
Usernames — used to build profiles and target you with personalised scams
Years of professional experience — may be combined with other breach data to build a profile for targeted attacks
Is the GeekedIn breach still dangerous in 2026?
Yes. Stolen data from the GeekedIn breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2016 are still actively used in credential stuffing attacks today.
Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your GeekedIn password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.
Frequently asked about the GeekedIn breach
Approximately 1,073,164 user records were exposed in the GeekedIn breach in August 2016.
Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your GeekedIn password elsewhere and haven't changed it, those accounts remain at risk today.
Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full GeekedIn dataset and tell you instantly whether your email was exposed and what data was taken.
Change your GeekedIn password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.
Who was affected by the GeekedIn breach?
The GeekedIn data breach affected approximately 1,073,164 users who had accounts with the service. While not the largest breach on record, it still represents a significant number of compromised accounts in our database of 970+ known breaches.
If you ever created an account with GeekedIn or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.
If your email was in the GeekedIn breach
Change your GeekedIn password immediately
Go to GeekedIn and change your password right now. Use a strong, unique password that you have never used anywhere else.
Change any account sharing that password
If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.
Enable two-factor authentication
Turn on 2FA on GeekedIn and every important account. Even if your password is known, attackers cannot get in without the second factor.
Check your other accounts for this breach
Run a full email check to see every breach your email appears in — not just this one.
searchCheck all my breaches — freeOther major breaches
Was my email hacked?
Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.
search Check my email now — it's freeNo signup required · Results in under 5 seconds · Your data is never stored