Intelimost 2019 Data Breach
The Intelimost 2019 data breach came from an exposed Elasticsearch server used to send personalized spam, not from an ordinary company customer database.
Exposed Data Types
2- Email addresses
- Passwords
About This Record
A security researcher found approximately 5 GB containing 11,535,164 records in March 2019, with the infrastructure linked to the mail.intelimost.com domain. A verified breach index reports 3,073,409 unique email addresses in the dataset. The record total and unique-email count are different measures and are not combined as a people count.
The verified data types are email addresses and plaintext passwords. The researcher and independent technical reporting observed an operation that used stolen mailbox credentials to log in, read recent sent messages, and generate spam using real subject and recipient context. That finding describes the operation's workflow; a match alone does not prove that every listed password worked, that a particular mailbox was accessed, or that messages were sent from that account.
Scope and evidence boundary
The 11,535,164 value counts operational records on the exposed server, while 3,073,409 is the verified unique-email count. Production has no import job or searchable person-level dataset linked to this incident. The sources do not report names, phone numbers, physical addresses, payment data, or identity documents. The passwords were reported as mailbox credentials, but no assumption is made that every row is current, accurate, or tied to a distinct person.
Safe next steps and archive link
If a person independently knows the password used for the relevant mailbox in 2019 and still uses the same or a similar password on an active account, replace the reused password with a unique one and enable multifactor authentication on the email account. Unfamiliar sessions, automatic forwarding rules, recovery details, and sent messages can also be reviewed. The Intelimost domain no longer resolves in DNS, so the company link points to a historical web archive; it is not a current support or security channel.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
