/
← Voltar ao feed

LimeLeads B2B leads database exposed via unsecured Elasticsearch in 2019 breach; 17.8M emails added to Have I Been Pwned

1 fonte(s) · 1 atualização(ões) · publicado 22/09/2026 05:02 · coletado há 1 dia

The now-defunct B2B marketing leads service LimeLeads suffered a data breach in August 2019 after an Elasticsearch server was left exposed and unsecured. The incident exposed tens of millions of records of largely corporate contact data, covering 17.8M unique email addresses. Have I Been Pwned added the dataset on 22 Sep 2026. The article does not attribute the incident to any threat actor.

Technical Details

  • Root cause: exposed, unsecured Elasticsearch server (no authentication stated).
  • Exposed data: email addresses, phone numbers, employers, job titles and geographic locations (state, city, postcode).
  • Breach occurred in August 2019; 17.8M addresses affected.

Remediation

  • Affected individuals should use a password manager to set strong, unique passwords, change any affected password and enable 2FA wherever supported.
  • As the data is corporate contact information, recipients should be alert to targeted phishing and social engineering.

Linha do tempo

  1. haveibeenpwned.com ↗ · pub. 22/09/2026 05:02 · coletado 19/10 17:56 primeiro registro

    LimeLeads B2B leads database exposed via unsecured Elasticsearch in 2019 breach; 17.8M emails added to Have I Been Pwned

    ler a análise desta fonte

    The now-defunct B2B marketing leads service LimeLeads suffered a data breach in August 2019 after an Elasticsearch server was left exposed and unsecured. The incident exposed tens of millions of records of largely corporate contact data, covering 17.8M unique email addresses. Have I Been Pwned added the dataset on 22 Sep 2026. The article does not attribute the incident to any threat actor.

    Technical Details

    • Root cause: exposed, unsecured Elasticsearch server (no authentication stated).
    • Exposed data: email addresses, phone numbers, employers, job titles and geographic locations (state, city, postcode).
    • Breach occurred in August 2019; 17.8M addresses affected.

    Remediation

    • Affected individuals should use a password manager to set strong, unique passwords, change any affected password and enable 2FA wherever supported.
    • As the data is corporate contact information, recipients should be alert to targeted phishing and social engineering.