Cristalix data breach

72,849 records Breach date: November 2017

Exposed data

Email addressesUsernamesPasswordsIP addresses

In November 2017, Cristalix suffered a data breach. The dataset indexed by LeakCheck contains 72,849 records.

The leaked records include email addresses, usernames, passwords and IP addresses.

If your data appears in this dataset, any account that shares the same password is at risk. Run a free check below, and if you find yourself in a leak — change the affected passwords and enable two-factor authentication.

Check if your account is affected

Enter your email, username or phone number — the check is free and confidential, and the result will tell you whether this breach mentions you.

Exposed in this breach? Do this now

Change the password

On the breached site and everywhere else you reused it. Make every password unique.

Enable 2FA

A second factor keeps a leaked password from becoming a hijacked account.

Set up monitoring

and get notified the moment your data appears in a new leak.

Cristalix breach: questions and answers

When did the Cristalix data breach happen?

The Cristalix breach dates to November 2017.

How many records were leaked in the Cristalix breach?

LeakCheck has indexed 72,849 records from the Cristalix breach.

What data was exposed in the Cristalix breach?

The leaked records include email addresses, usernames, passwords and IP addresses.

Were passwords exposed in the Cristalix breach?

Yes. The indexed Cristalix records include passwords, in plain text or hashed. If you had an account, change that password and every other password you reused.

How do I check if my data was in the Cristalix breach?

Enter your email address, username or phone number in the search form on this page. The free check shows whether your data appears in the Cristalix breach — and in any of the other 1,468 sources LeakCheck indexes.

What should I do if my data was in the Cristalix breach?

Change the password you used on Cristalix and everywhere you reused it, turn on two-factor authentication, and watch for phishing that quotes details from the leak. To hear about the next breach first, set up breach monitoring.