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.
When did it happen?
The breach date in the public record is January 1, 2017. The record was added to the catalogue on December 9, 2018 and last updated there on December 9, 2018.
What information was reported as exposed?
- Email addresses
- Passwords
These are incident-level categories. The record does not prove that every category was exposed for every affected person.
Who may be affected?
This record may be relevant to people who had an account or other relationship with Hub4Tech or used hub4tech.com around January 1, 2017. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.
What should you do?
Compare the organization, dates, and information categories with any notice you received. Use contact details you independently confirm.
Change exposed or reused passwords, begin with your email account, and turn on multi-factor authentication where available.
Treat unexpected breach follow-ups with caution. Do not use links or phone numbers in a suspicious message; contact the organization directly.
Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.
Sources and review information
- Have I Been Pwned breach catalogue record ↗
- Federal Trade Commission: What To Do After a Data Breach ↗
- Federal Trade Commission: Credit Freezes and Fraud Alerts ↗
Page reviewed September 14, 2026 by the Data Breach Help Editorial Team. Catalogue details reflect the provider record and may change.