Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Exposed Elasticsearch Sales Leads Database on AWS Leaks 5.8 M Personal Records

A misconfigured Elasticsearch cluster on AWS publicly exposed 5.8 M sales‑lead records, including names, emails and addresses. The incident highlights the need for continuous configuration monitoring and auditable evidence of cloud‑asset controls.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
High
🏢
Affected
3 sector(s)
✅
Actions
4 recommended
📰
Source
haveibeenpwned.com

Exposed Elasticsearch Sales Leads Database on AWS Leaks 5.8 M Personal Records

What Happened — In October 2018 security researcher Bob Diachenko discovered an unauthenticated Elasticsearch cluster hosted on AWS that exposed a sales‑lead dataset containing 5,788,169 unique records. The index held names, personal email addresses, employer names and physical addresses. No owner could be identified, so the breach is catalogued as “Elasticsearch Sales Leads”.

Why It Matters for Trust & Control Assurance

  • Unprotected cloud data stores illustrate the exact gap a continuous control‑assurance program is built to detect: missing access restrictions and inadequate configuration monitoring.
  • Demonstrating that you have automated evidence of cloud‑asset inventory, authentication enforcement, and change‑control logs provides a defensible audit trail for regulators and partners.
  • Mapping this incident to the control objective of secure configuration management satisfies multiple frameworks simultaneously, reinforcing trust with customers.

Who Is Affected – Companies that store or purchase bulk sales‑lead data (marketing SaaS platforms, B2B lead‑generation services, and any organization that leverages cloud‑hosted Elasticsearch for customer data).

Recommended Actions –

  • Conduct an immediate inventory of all Elasticsearch (or similar NoSQL) endpoints across your cloud environment.
  • Enforce strong authentication and network‑level access controls (VPC, security groups, IAM policies).
  • Deploy continuous configuration‑monitoring tools that capture and retain evidence of security‑group and access‑policy changes.
  • Map the “secure configuration” control to your framework of record and collect the supporting logs for audit readiness.

Source: Have I Been Pwned – Elasticsearch Sales Leads breach

Technical Notes – The exposure resulted from a misconfigured Elasticsearch service that allowed anonymous HTTP GET requests. No known vulnerability (CVE) was exploited; the breach is purely a cloud‑misconfiguration issue. Data types leaked: email addresses, full names, employer names, and physical mailing addresses.

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/ElasticsearchSalesLeads ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Misconfigurations are control gaps in disguise.

Verisq AI Trust Operations turns findings like this into mapped controls with continuous evidence, keeping your audit readiness current instead of point-in-time.

Map your controls with Verisq AI Trust Operations →