What was exposed, when it happened, and which databases confirm it.
- accounts
- 1,073,164
- Breached
- August 15, 2016
- Last Update
- March 6, 2022
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.
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.
Compromised Info
- Email addresses
- Geographic locations
- Names
- Professional skills
- Usernames
- Years of professional experience
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- HIBP
FAQ
What was leaked in the GeekedIn breach?
The GeekedIn breach exposed: Email addresses, Geographic locations, Names, Professional skills, Usernames, and Years of professional experience.
When did the GeekedIn breach happen?
The GeekedIn breach was disclosed on August 15, 2016 and affected 1,073,164 records.
Am I affected by the GeekedIn breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the GeekedIn leak.