GeekedIn
HighIn 2016, GeekedIn exposed a database containing over 1M users' sensitive professional information.
- Records exposed
- 1,073,164 records
- Breach date
- Breach Aug 15, 2016
- Last update
- Updated Mar 6, 2022
What data was exposed?
Fields reported as compromised in this breach record.
Why does this breach matter?
In-depth analysis of the breach and its implications.
In August 2016, data related to over 1 million profiles from GeekedIn, a technology recruitment platform, was compromised due to an unsecured MongoDB database. This data, which included user email addresses, names, professional skills, and locations, had originally been sourced from public profiles on GitHub, contrary to its terms of use. The exposed database became accessible to unauthorized individuals, resulting in the extraction of sensitive user information.
Impact Analysis
Understanding the scope and consequences of this breach.
- User Impact
- Users risked targeted phishing, spam, and possible unauthorized exploitation of their professional identities.
- Business Impact
- The breach could have impacted GeekedIn's credibility and compliance standing.
- Affected Sectors
- Technology Recruitment
- Professional Networking
- Geographic Impact
- Global
What You Should Do
Recommended actions to take in response to this breach.
If You Were Affected
- •Change your password across platforms associated with the exposed email.
- •Monitor your email for any phishing attempts.
Preventive Measures
- •Be cautious of public data sharing through third-party services.
- •Ensure accounts are secured against misuse, even when data is public.
Frequently Asked Questions
Common questions about this breach and what it means for you.