DLH.net Data Breach (2016): What Was Exposed & What To Do

Inside the incident

In July 2016, DLH.net experienced a data breach that exposed records belonging to 3.3 million subscribers. The exposed material included email addresses, names, dates of birth, usernames, website activity, and passwords stored as salted MD5 hashes. The breach also disclosed keys used to redeem and activate games on the Steam platform. The data set was later provided to the Have I Been Pwned service by the monitoring project Vigilante.pw.

How a breach like this happens

Incidents involving subscriber databases at online services often begin with unauthorised access to servers or applications that store user records. Attackers may exploit vulnerabilities in web applications, obtain credentials through other means, or locate unprotected backups. Once inside, they can copy tables containing account details and authentication data. In many cases the stolen material is later shared or sold, after which it appears in public breach repositories.

About DLH.net

DLH.net operated as a gaming news site that maintained subscriber accounts. Organisations in this sector routinely collect registration information to manage user profiles, deliver newsletters, and facilitate game-related services such as Steam key distribution. A breach at such a site is consequential because the records combine contact details with credentials and identifiers that remain useful for years after the event.

The information in question

The breach exposed dates of birth, email addresses, names, passwords, usernames, and website activity. The records also contained Steam game activation keys and passwords stored as salted MD5 hashes. No further detail on the precise file contents or additional data fields has been publicly disclosed beyond these categories.

What's at stake

Exposed email addresses and usernames can be used for targeted phishing or to link accounts across services. Dates of birth and names add to the information available for identity verification processes. Password hashes, even when salted, may be processed offline in attempts to recover plaintext credentials, which could then be tested against other sites where the same password was reused. Steam keys carry the risk of unauthorised redemption if they had not already been used. For the organisation, the incident created long-term reputational and operational consequences associated with managing subscriber trust after a large-scale exposure.

What to do if you're exposed

Review any DLH.net account for current status and change the password if the service remains active. Use a different password for every account and enable multi-factor authentication where available. Monitor email for unexpected login attempts or password-reset messages. Readers can run a free exposure scan by entering their email address in a breach-checking service to see whether their information appears in known data sets.

AICompiled with AI assistance from public sources and published under our editorial standards.