What happened?
In July 2016, the gaming news site DLH.net suffered a data breach which exposed 3.3M subscriber identities. Along with the keys used to redeem and activate games on the Steam platform, the breach also resulted in the exposure of email addresses, birth dates and salted MD5 password hashes. The data was donated to Have I Been Pwned by data breach monitoring service Vigilante.pw .
When did it happen?
The breach date in the public record is July 31, 2016. The record was added to the catalogue on September 7, 2016 and last updated there on September 7, 2016.
What information was reported as exposed?
- Dates of birth
- Email addresses
- Names
- Passwords
- Usernames
- Website activity
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 DLH.net or used dlh.net around July 31, 2016. 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.