Hub4Tech data breach

Breach date: 2017-01-01. Added to this index: 2018-12-09. Accounts affected: about 37K. Domain: hub4tech.com.

What happened

On an unknown date in approximately 2017, the Indian training and assessment service known as Hub4Tech suffered a data breach via a SQL injection attack. The incident exposed almost 37k unique email addresses and passwords stored as unsalted MD5 hashes. No response was received from Hub4Tech when contacted about the incident.

Breach data sourced from Have I Been Pwned, used under CC BY 4.0. Additional breach metadata provided by XposedOrNot. DataExposed is an independent service and is not affiliated with or endorsed by either.

What was exposed

  • Email addresses: The email address you used to register or log in. It is the most common field in breaches because it doubles as your username on most sites.
  • Passwords: The secret you use to sign in, stored by the breached service either in plain text, in a scrambled form called a hash, or encrypted. How it was stored decides how quickly it can be recovered.

What to do now

  1. Check whether your own address is in this dataset with the free email breach check.
  2. Change the password on this service and every other site where you used the same password.
  3. Turn on two-factor authentication on your email account first, because it is the reset path for everything else.
  4. Treat calls and messages that quote real details about you as hostile until you verify them another way.

Frequently asked questions

What data was leaked in the Hub4Tech breach?

The Hub4Tech breach exposed Email addresses, Passwords. About 37K accounts were affected.

Was I affected by the Hub4Tech breach?

Run the free email breach check with the address you used on that service. It will tell you whether your address appears in this dataset.

What should I do about the Hub4Tech breach?

Change the password on that account and everywhere you reused it, then turn on two-factor authentication. Passwords from this breach are traded and tried automatically against other sites.

Next steps