Lucian Constantin
CSO Senior Writer

A hacker is selling 167 million LinkedIn user records

news
May 18, 20163 mins

The data includes hashed passwords for 167 million accounts and likely dates back to 2012

A hacker is trying to sell a database dump containing account records for 167 million LinkedIn users.

The announcement was posted on a dark market website called TheRealDeal by a user who wants 5 bitcoins, or around $2,200, for the data set that supposedly contains user IDs, email addresses and SHA1 password hashes for 167,370,940 users.

According to the sale ad, the dump does not cover LinkedIn’s complete database. Indeed, LinkedIn claims on its website to have over 433 million registered members.

Troy Hunt, the creator of Have I been pwned?, a website that lets users check if they were affected by known data breaches, thinks that it’s highly likely for the leak to be legitimate. He had access to around 1 million records from the data set.

“I’ve seen a subset of the data and verified that it’s legit,” Hunt said via email.

Lucian Constantin

A hacker is selling 167 million stolen LinkedIn account records on a dark market website.

LinkedIn suffered a data breach back in 2012, which resulted in 6.5 million user records and password hashes being posted online. It’s highly possible that the 2012 breach was actually larger than previously thought and that the rest of the stolen data is surfacing now.

LinkedIn did not immediately respond to a request for comment.

Attempts to contact the seller failed, but the administrators of LeakedSource, a data leak indexing website, claim to also have a copy of the data set and they believe that the records do originate from the 2012 LinkedIn breach.

“Passwords were stored in SHA1 with no salting,” the LeakedSource administrators said in a blog post. “This is not what internet standards propose. Only 117m accounts have passwords and we suspect the remaining users registered using FaceBook or some similarity.”

Best security practices call for passwords to be stored in hashed form inside databases. Hashing is a one-way operation that generates unique, verifiable cryptographic representations of a string that are called hashes.

Hashing is useful for validating passwords, because running a password through the same hashing process should always result in the same hash, allowing its comparison with one previously stored in a database.

Converting a hash back into the original password should be impossible, which is why it’s safer to store hashes instead of plain text passwords. However, there are old hashing functions, such as MD5 and SHA1, that are vulnerable to various cracking techniques and should no longer be used.

When the 6.5 million LinkedIn password hashes were leaked in 2012, hackers managed to crack over 60 percent of them. The same thing is likely true for the new 117 million hashes, so they cannot be considered safe.

Worse still, it’s very likely that many LinkedIn users that were affected by this leak haven’t changed their passwords since 2012. Hunt was able to verify that for at least one HIBP subscriber whose email address and password hash was in the new data set that is now up for sale.

Many people affected by this breach are also likely to have reused their passwords in multiple places on the Web, Hunt said via email.

LinkedIn users who haven’t changed their passwords in a long time, are advised to do so as soon as possible. Turning on LinkedIn’s two-step verification is also recommended. If the LinkedIn password has been used on other websites, it should be changed there as well.

Lucian Constantin

Lucian Constantin writes about information security, privacy, and data protection for CSO. Before joining CSO in 2019, Lucian was a freelance writer for VICE Motherboard, Security Boulevard, Forbes, and The New Stack. Earlier in his career, he was an information security correspondent for the IDG News Service and Information security news editor for Softpedia.

Before he became a journalist, Lucian worked as a system and network administrator. He enjoys attending security conferences and delving into interesting research papers. He lives and works in Romania.

You can reach him at lucian_constantin@foundryco.com or @lconstantin on X. For encrypted email, his PGP key's fingerprint is: 7A66 4901 5CDA 844E 8C6D 04D5 2BB4 6332 FC52 6D42

More from this author