MyRecon OSINTData Enrichment Exposure From PDL Customer
On 16 October 2019, Data Enrichment Exposure From PDL Customer was breached. 622,161,052 accounts were exposed, including email addresses, employers, geographic locations. MyRecon rates it 79/100 — severe. That is about 1.8× the population of the United States.
Nobody in this file signed up for anything. Data enrichment companies do not collect from you; they buy, scrape and merge from everywhere else, then sell a composite profile to businesses that want to know more about the people already in their own database. The 622 million people here were the product, not the customers.
The detail that makes it worse is where it was found. The exposed server was not the enrichment company's — it belonged to one of its customers, who had left an Elasticsearch instance on the open internet with no password. So the data was assembled by one company, sold to a second, and exposed by the second, and there was no point in that chain at which any of the 622 million people could have been asked or told.
That chain is the reason this record is worth reading even though the fields look mundane. Name, employer, job title, phone number, location and social profiles is a background check, and it is the raw material for convincing approaches that appear to come from a colleague or a recruiter. If you want to understand how the industry that built it works, the guide on how data brokers turn a leak into a profile covers it.
What happened
In October 2019, security researchers Vinny Troia and Bob Diachenko identified an unprotected Elasticsearch server holding 1.2 billion records of personal data. The exposed data included an index indicating it was sourced from data enrichment company People Data Labs (PDL) and contained 622 million unique email addresses. The server was not owned by PDL and it's believed a customer failed to properly secure the database. Exposed information included email addresses, phone numbers, social media profiles and job history data.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
Who was behind it
No party has been publicly confirmed as responsible, and this page will not name one. Most breaches are never formally attributed: data surfaces on a forum or inside a combined dump long after the intrusion, and the trail back to a specific actor is rarely made public. Where a group has claimed responsibility it is usually named in the account above — that claim is theirs, not a finding of ours.
What was exposed, and why it matters
- Email addressesThe address becomes a confirmed, active target — expect more phishing, better aimed.
- EmployersConnects a personal account to a workplace, which is how attackers pivot from a person to a company.
- Geographic locationsWhere the account was used, which narrows a person down further than most people expect.
- Job titlesIdentifies who has access to what, which is how targets for business email compromise are picked.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- Phone numbersEnables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
- Social media profilesAdds detail to a profile that can be assembled from several breaches at once.
What to do if you were in it
- Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
- Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.
Questions people ask about this breach
Was my email address in the Data Enrichment Exposure From PDL Customer breach?
Enter it in the box at the top of this page. MyRecon checks it against this breach and every other one on record, and the address is never stored.
What data was leaked in the Data Enrichment Exposure From PDL Customer breach?
email addresses, employers, geographic locations, job titles, names, phone numbers, social media profiles. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 16 October 2019. It was published to Have I Been Pwned on 22 November 2019, a gap of 38 days during which the data was already out.
Is the Data Enrichment Exposure From PDL Customer breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
622,161,052 accounts. That is about 1.8× the population of the United States. That is accounts rather than people — one person often has several.
Read next
Also in the archive
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself — every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.