Breach registry
ApexSMS Data Breach
What was exposed, when it happened, and which databases confirm it.
- accounts
- 23,246,481
- Breached
- April 15, 2019
- Last Update
- September 21, 2023
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 May 2019, news broke of a massive SMS spam operation known as "ApexSMS" which was discovered after a MongoDB instance of the same name was found exposed without a password. The incident leaked over 80M records with 23M unique email addresses alongside names, phone numbers and carriers, geographic locations (state and country), genders and IP addresses.
Compromised Info
- Email addresses
- Genders
- Geographic locations
- IP addresses
- Names
- Phone numbers
- Telecommunications carrier
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- Dehashed— linked via domain matching
- HIBP
FAQ
What was leaked in the ApexSMS breach?
The ApexSMS breach exposed: Email addresses, Genders, Geographic locations, IP addresses, Names, Phone numbers, and Telecommunications carrier.
When did the ApexSMS breach happen?
The ApexSMS breach was disclosed on April 15, 2019 and affected 23,246,481 records.
Am I affected by the ApexSMS breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the ApexSMS leak.