Breach date: 2016-08-15. Added to this index: 2016-11-17. Accounts affected: about 1.1M. Domain: geekedin.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.
Breach data sourced from Have I Been Pwned, used under CC BY 4.0. Additional breach metadata provided by XposedOrNot. DataExposed is an independent service and is not affiliated with or endorsed by either.
What was exposed
Email addresses: The email address you used to register or log in. It is the most common field in breaches because it doubles as your username on most sites.
Geographic locations: A general location recorded on your account, such as a country, state, city, postcode or region, either typed in by you or estimated from your IP address.
Names: Your first name, surname and sometimes middle name or initials, as you gave them when you signed up. It appears in almost every breach because nearly every account asks for it.
Professional skills: The skills, certifications, tools and specialisms listed on a resume, job board or professional networking profile.
Usernames: The handle or login name you chose for an account, which may be public on forums, games and social platforms or used privately to sign in.
Years of professional experience: The number of years you have worked in a profession, industry or role, stored on job sites, resumes, professional networks or recruitment systems.
What to do now
Check whether your own address is in this dataset with the free email breach check.
Review the accounts connected to this service and turn on two-factor authentication.
Turn on two-factor authentication on your email account first, because it is the reset path for everything else.
Treat calls and messages that quote real details about you as hostile until you verify them another way.
Frequently asked questions
What data was leaked in the GeekedIn breach?
The GeekedIn breach exposed Email addresses, Geographic locations, Names, Professional skills, Usernames, Years of professional experience. About 1.1M accounts were affected.
Was I affected by the GeekedIn breach?
Run the free email breach check with the address you used on that service. It will tell you whether your address appears in this dataset.
What should I do about the GeekedIn breach?
Treat any message that quotes details from this breach as suspicious, turn on two-factor authentication, and consider removing your details from people-search sites if your address or phone was included.