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.
Dirtycode.io breach: questions and answers
When did the Dirtycode.io data breach happen?
The Dirtycode.io breach dates to May 2020.
How many records were leaked in the Dirtycode.io breach?
LeakCheck has indexed 22,250 records from the Dirtycode.io breach.
What data was exposed in the Dirtycode.io breach?
The leaked records include email addresses, usernames, passwords and geographic locations.
Were passwords exposed in the Dirtycode.io breach?
Yes. The indexed Dirtycode.io 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 Dirtycode.io 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 Dirtycode.io breach — and in any of the other 1,468 sources LeakCheck indexes.
What should I do if my data was in the Dirtycode.io breach?
Change the password you used on Dirtycode.io 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.