Hackers Sell Personal LinkedIn Data From Leak Affecting 700M Users

Hackers are selling the personal information of over 700 million LinkedIn users. Here are the data types that were leaked:

Email Addresses; Full names; Phone numbers; Physical addresses; Geolocation records; LinkedIn username and profile URL; Personal and professional experience/background; Genders; Other social media accounts and usernames

On June 22nd, a user of a popular hacker forum advertised data from 700 Million LinkedIn users for sale. The user of the forum posted a sample of the data that includes 1 million LinkedIn users.

LinkedIn Data Leak of 500 Million People Sold Online

Just days after a Facebook data leak was discovered, security researchers found another one, this time involving LinkedIn. It affects a similar amount of users, 500 million, with data being sold on a “popular hacker forum.”

The leaked files appear to only contain LinkedIn profile information – we did not find any deeply sensitive data like credit card details or legal documents in the sample posted by the threat actor. With that said, even an email address can be enough for a competent cybercriminal to cause real damage.

LinkedIn Violates Library Privacy With LinkedIn Learning

Many states have laws in place to protect the privacy of libraries. But LinkedIn is violating this with LinkedIn Learning, formerly known as Lynda.com.

Currently, when Lynda.com is accessed through a library, a user logs in with her or his library card and a PIN. No other personal information is required.

Under the new LinkedIn Learning policy, library users would be required to create a personal, publicly searchable, profile and agree to LinkedIn’s user agreement and privacy policy before being able to use LinkedIn Learning.

Checking off the user agreement grants LinkedIn the power to share the information contained in a personal profile with whoever LinkedIn wants.

Libraries are a bastion against corporations, where you can get free resources and just hang out without having to buy anything. I hope this gets resolved in the library’s favor.