Professional emails, phone numbers, salary estimates… all of this information accumulated during the data breach.
Sell this data to LinkedIn It affects almost all users. Of the 756 million claimed by Microsoft’s professional platform, 700 million will be affected, or 92% of all accounts.
On this professional social network, members are in contact with their colleagues, other professionals and potential recruits, thus posting their CVs or information about their previous positions in companies. According to the website specialized in cyber security, RestorePrivacyA hacker offered their data for sale on a popular hacker’s forum, exposing a data sample from 1 million users. RestorePrivacy analyzed the nature of the stolen data: email addresses, identity, phone numbers, postal address, salary estimates, and social media account identifiers. This data is original and actually comes from LinkedIn accounts.
Accumulation of old data
Last April, 500 million users of the social network witnessed a data breach. According to another website that specializes in cyber security, PrivacySharksThis new sale appears to be an accumulation of data from previous leaks. LinkedIn said in a statement:We want to be clear that this is not a data breach and that no private data has been disclosed to LinkedIn members. Our initial investigation found that it was pulled from LinkedIn and other sites and includes the same data that was reported earlier this year in April 2021.»
All this information allows cyber criminals To carry out “phishing” attacks, i.e. sending fraudulent emails to extract other data from users who are victims of their data leakage. This precise information about you can be used either to extract funds or to gain access to a company’s information system. More seriously, cybercriminals have the potential to usurp your identity by creating fake profiles using your data. To get around these issues, don’t click on questionable links that appear on certain emails and don’t enter your bank account details on a site whose link doesn’t start with “https:».