Elasticsearch Sales Leads (AWS, unidentified owner) Data Compilation (2018)
A data brokers service in the data & identity sector.
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Childhood minimum is an observed minimum on data that includes children; read it as a low floor, because the rating does not yet count how long a child carries the exposure. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes data that locates or profiles a person, beyond contact details.
- Circulating
- 5,788,169 email addresses
- Field types
- 4 seen
- Breach date
- Not established
- Observed as of
- Nov 17, 2026
Breach date not established8 years laterListed in breach cataloguesObserved · scored
What data was exposed
How this data can be used against you
Physical targeting
Links a named person to where they live or go.
Social engineering
Contact details plus enough context for a convincing approach.
Identity
No usable identity package in what circulates.
Account access
No usable login material in what circulates.
Financial
No usable financial detail in what circulates.
Coercion
Nothing in what circulates is sensitive enough for leverage.
Health
No medical detail in what circulates.
Crypto
Nothing in what circulates is tied to crypto assets.
One key action to take
Assume your home address is findable
Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
How this breach happened
In October 2018 researcher Bob Diachenko found several open databases with several hundred million records between them. One of them, an Elasticsearch server hosted on AWS, held business sales leads with 5.8 million unique email addresses.
The records named individuals and their employers, with company addresses and contact details. The owner of the database was never identified, so the set carries a descriptive name.
What has happened since the breach
The Elasticsearch Sales Leads (AWS) dataset circulated publicly; treat as part of the standing exposure landscape.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Circulating
- Observed as of
- Nov 17, 2026
- Breach date
- Not established
- Volume
- 5,788,169 email addresses
- Fields seen
- 4email address, employer, full name, physical address
The score is built only on what is seen circulating.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Circulating |
|---|---|---|---|
| Email Address | Lasts for years | No | Yes |
| Employer | Fades over a few years | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Physical address | Lasts for years | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
Practical risk: addresses enable physical targeting and mail fraud. Compounding risk rises where this data links to other breached or brokered records.
Risks for executives and other high-profile people
A data-broker/identity breach: aggregated identity attributes re-seed broker networks and enrich targeting of the individual. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.
Who is behind this breach
No threat actor has been publicly attributed.
About this record
This is a compilation: a circulating dataset assembled from many sources, not a breach of the organization named. It is scored because the data circulates, whatever its origin. Circulation was last verified on Nov 17, 2026. The rating was last computed on Nov 17, 2026. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.