EpicBot

epicbot.com

816,150
Exposed Records
Sep 2019
Breach Date
6 years ago
Hard to Crack
Password Risk
Entertainment industry
Entertainment
Industry
Added to XposedOrNot on November 8, 2023 · #430 of 763 breaches by records exposed

About This Breach

EpicBot, a popular gaming botting program, suffered a data breach in 2019 that exposed the personal information of more than 800,000 users. The stolen data included usernames, email addresses, and passwords (stored as SHA-1 hashes). The breach was believed to have been caused by a SQL injection attack on EpicBot's servers.

Data Exposed

Email addresses
Usernames
Passwords
IP addresses

Breach Details

Breach Type Data Breach
Searchable Yes
Verified Yes
Sensitive Data No
Reference https://www.bitdefender.com/blog/hotforsecurity/gatehub-and-epicbot-hacked-2-2-million-user-accounts-leaked/ (opens in new tab)

Frequently Asked Questions

When did the EpicBot data breach happen?

EpicBot was breached in Sep 2019. The breach was added to the XposedOrNot index on November 8, 2023.

How many records were exposed in the EpicBot breach?

816,150 records were exposed, making it the #430 largest of the 763 breaches in our index.

What data was exposed in the EpicBot breach?

The exposed data includes: Email addresses, Usernames, Passwords, IP addresses.

What should I do if I was affected by the EpicBot breach?

Change your password on the affected service (and anywhere you reused it), turn on two-factor authentication, and set up free breach alerts on XposedOrNot so you know the moment your email appears in a new breach.

What Should You Do?

Urgent

Change Your Passwords

Update your password immediately, using 12+ characters with numbers and symbols.

High Priority

Enable Two-Factor Authentication

Add 2FA on all supported accounts using an authenticator app like Google Authenticator or Authy.

Recommended

Review Device Security

Update your devices and browsers, and check for unauthorized logins.

Recommended

Monitor Your Accounts

Set up login alerts and review account activity regularly for suspicious access.

Best Practice

Use a Password Manager

Never reuse passwords: use a password manager to generate unique ones for each account.