Classic site
db8151dd logo

Breach registry

db8151dd Data Breach

Covve

covve.com

What was exposed, when it happened, and which databases confirm it.

VerifiedNo Passwords Leaked
accounts
22,802,117
Breached
February 20, 2020
Last Update
May 19, 2020

Were you caught in this breach?

Search your email, phone number or username against every record CheckLeaked indexes.

Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.

What happened

In February 2020, a massive trove of personal information referred to as "db8151dd" was provided to HIBP after being found left exposed on a publicly facing Elasticsearch server. Later identified as originating from the Covve contacts app, the exposed data included extensive personal information and interactions between Covve users and their contacts. The data was provided to HIBP by dehashed.com.

Compromised Info

  • Email addresses
  • Job titles
  • Names
  • Phone numbers
  • Physical addresses
  • Social media profiles

Attestation

Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.

HIBP22,802,117
DEHASHED22,802,117
LEAKCHECKnot attested
VIGILANTEnot attested

Sources & Link Methods

  • HIBP

FAQ

What was leaked in the db8151dd breach?

The db8151dd breach exposed: Email addresses, Job titles, Names, Phone numbers, Physical addresses, and Social media profiles.

When did the db8151dd breach happen?

The db8151dd breach was disclosed on February 20, 2020 and affected 22,802,117 records.

Am I affected by the db8151dd breach?

Search your email, phone or username at checkleaked.cc to find out whether your data appears in the db8151dd leak.

Advertising choice

Google Analytics stays active. Allow Google Ads, LinkedIn Ads and Reddit Ads to measure purchases and personalize advertising? Your choice won’t affect search or purchases. You can change it in Settings.

Privacy policy