Data & Identity · Data Brokers

Elasticsearch Sales Leads (AWS, unidentified owner) Data Compilation (2018)

A data brokers service in the data & identity sector.

Compilation record · not a breach of a named organization · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
Not yet scored
Circulation not yet audited
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. 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 →

Data sensitivity
Sensitive

Includes data that locates or profiles a person, beyond contact details.

Volume
Count not yet verified
Field types
4 listed
Breach date
Oct 2018
Vector
Database Exposure
Catalogued by Have I Been Pwned
How it unfoldedAbout a month from breach to listing
  1. Breach
  2. Listed in breach catalogues
What came out

What data was exposed

Home addressWhere you sleep
Email AddressContact
EmployerProfessional
Full NameIdentity
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material · Field list from breach catalogues, not yet verified
What it enables

How this data can be used against you

Assessed once the record is scored.

What you should do

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 it yourself

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.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

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 →
Full record · 7 sections

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
No sign-in · nothing is recorded
What happened

How this breach happened

In October 2018, security researcher Bob Diachenko identified multiple exposed databases with hundreds of millions of records. One of those datasets was an Elasticsearch instance on AWS containing sales lead data and 5.8M unique email addresses. The data contained information relating to individuals and the companies they worked for including their names, email addresses and company name and contact information.

Recent developments

What has happened since the breach

The Elasticsearch Sales Leads (AWS) dataset circulated publicly; treat as part of the standing exposure landscape.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Not yet researched
Not yet verified by ObscureIQ

Listed in breach catalogues

Breach date
Oct 2018
Volume
Count not yet verified
Fields listed
4email address, employer, full name, home address

The score is built only on what is listed in circulation.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeListed
Email AddressLasts for yearsNoYes
EmployerFades over a few yearsNoYes
Full NameLasts for yearsNoYes
Home addressLasts for yearsNoYes

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.

Downstream risk

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.

Principal risk advisory

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.

Threat actor

Who is behind this breach

No threat actor has been publicly attributed.

Database ExposureCybercrime & CompilationsData CompilationNo single organization2018

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. No score is shown until the circulating field list has been audited. 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.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI