D-apteka.ru data breach

40,987 records Breach date: August 2024 no passwords

Exposed data

Email addressesUsernamesNamesPhone numbers

In August 2024, D-apteka.ru suffered a data breach. The dataset indexed by LeakCheck contains 40,987 records.

The leaked records include email addresses, usernames, names and phone numbers.

The indexed records do not include passwords, but the details they hold can still be used for phishing. Run a free check below to see whether you are affected.

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.

D-apteka.ru breach: questions and answers

When did the D-apteka.ru data breach happen?

The D-apteka.ru breach dates to August 2024.

How many records were leaked in the D-apteka.ru breach?

LeakCheck has indexed 40,987 records from the D-apteka.ru breach.

What data was exposed in the D-apteka.ru breach?

The leaked records include email addresses, usernames, names and phone numbers.

Were passwords exposed in the D-apteka.ru breach?

No. The records indexed from D-apteka.ru do not include passwords — but the other details they hold can still be used for phishing.

How do I check if my data was in the D-apteka.ru 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 D-apteka.ru breach — and in any of the other 1,469 sources LeakCheck indexes.

What should I do if my data was in the D-apteka.ru breach?

Change the password you used on D-apteka.ru 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.