Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
Breach occurred 2016-08-15Verifiedgeekedin.net
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.
Data exposed
Frequently asked questions
The GeekedIn data breach occurred on August 15, 2016. It was added to Have I Been Pwned's breach catalog on November 17, 2016.
1,073,164 accounts were affected by the GeekedIn data breach, according to Have I Been Pwned's records.
The GeekedIn breach exposed the following data types: Email addresses, Geographic locations, Names, Professional skills, Usernames, Years of professional experience.
Yes. Have I Been Pwned has verified the GeekedIn breach, meaning there's confirmed evidence the exposed data is genuine and tied to real accounts.
Use KazaSec's free Email Breach Checker (/tools/breach-check) to check whether a specific email address has surfaced in the GeekedIn breach, or any other known breach — the tool never stores what you search.
Our free Email Breach Checker tells you whether a specific email address has surfaced in this breach — or any other known breach — without ever storing what you search.
Check your email →Talk to us about this
We help organizations find and fix the gaps that lead to a breach, before they do.