Data breach · August 2016

Was I in the GeekedIn data scrape?

Data about 1,073,164 users was collected from GeekedIn, a technology recruitment site, in August 2016. It included email addresses, general locations, names and professional skills and 2 other kinds of detail. If you had an account there by August 2016, check your address below to see whether it is one of them.

Breach record last updated . Steps read from the government pages at the foot of this page.

01

What happened?

In August 2016, GeekedIn, a tech recruiting site, left a MongoDB database open, and an unknown party copied its records. The data had first been scraped from public GitHub profiles against that site's terms. It included email addresses of many GitHub members.

Organisation
GeekedIn, a technology recruitment site (geekedin.net)
When it happened
August 2016
Added to monitored breach databases
17 November 2016
Accounts in the data
1,073,164
What was exposed
email addresses, general locations, names, professional skills, usernames and years of professional experience
02

What was exposed, and what does it mean for me?

  • Your email addressemail addresses

    Expect messages that look like they come from this service or another one you use, written to get you to click a link or sign in on a fake page.

  • Other detailsgeneral locations, names, professional skills, usernames and years of professional experience

    On their own these carry less risk, but they make a scam message sound more personal.

03

What should I do now?

In this order, for what this data scrape exposed.

1. Expect phishing

  • Be wary of messages that urge you to act fast, ask for personal details, or link to an address that is slightly off.
  • If a message might be genuine, do not use its links or phone numbers. Go to the site by typing its address yourself.
04

Is my address in it?

Enter your email address. We check that one address against monitored breach databases and show which breaches list it and what each exposed.

No account needed. We keep the address you check, when, and how many breach records it was found in, to prevent abuse, until you ask us to delete it. Privacy

Sources

Where does this come from?

Other breaches from 2016