
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
covve.com
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.
Data exposed
Frequently asked questions
The Covve data breach occurred on February 20, 2020. It was added to Have I Been Pwned's breach catalog on May 15, 2020.
22,802,117 accounts were affected by the Covve data breach, according to Have I Been Pwned's records.
The Covve breach exposed the following data types: Email addresses, Job titles, Names, Phone numbers, Physical addresses, Social media profiles.
Yes. Have I Been Pwned has verified the Covve breach, meaning there's confirmed evidence the exposed data is genuine and tied to real accounts.
Use KazaSec's free Email Breach Checker (/tools/breach-check) to check whether a specific email address has surfaced in the Covve breach, or any other known breach — the tool never stores what you search.
Our free Email Breach Checker tells you whether a specific email address has surfaced in this breach — or any other known breach — without ever storing what you search.
Check your email →Talk to us about this
We help organizations find and fix the gaps that lead to a breach, before they do.