Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

LinkedIn Users: Change Password Now

Attackers appear to have obtained--and may have already decrypted--at least 6.5 million LinkedIn passwords.

All users of the LinkedIn social network should immediately change their password.

Security experts began broadcasting that warning Wednesday after reports emerged that nearly 6.5 million LinkedIn password hashes--encrypted using SHA1, but not salted--had been posted to a Russian hacking forum on Monday, together with a request to help decrypt them.

Hackers have already reported breaking 163,267 of the passwords, reported Norwegian news outlet Dagen IT, which Wednesday broke the news of the LinkedIn password breach.

LinkedIn confirmed that it's investigating the potential password breach. "Our team is currently looking into reports of stolen passwords. Stay tuned for more," read a Wednesday tweet from LinkedIn News.

[ Read about how hackers accessed a Romney Webmail account. See Romney Campaign Investigates Hotmail Account Hack. ]

What should LinkedIn users do? "First change your LinkedIn password. Then prepare for scam emails about Linkedin password changes, linking to phishing sites. Will happen," said Mikko Hypponen, chief research officer at F-Secure, via Twitter.

Security expert Per Thorsheim tweeted that he'd reviewed the uploaded password hashes and recovered at least 300,000 of them. "The number of [occurrences] of 'linkedin' in those passwords leave little doubt about the origin. Change password NOW!" Meanwhile, a post from the Security Ninja website's Twitter feed noted that "after getting the list of @linkedin hashes and hashing my old pwd with no salt there is a match for the hash in the list." Accordingly, it said that it was "best to assume the worst and change your password."

Evidently, LinkedIn didn't salt its passwords--a practice recommended by security experts that involves adding a unique string to each password before encrypting it. Had the passwords been salted, it would have made them more difficult for attackers to reverse the SHA1 password hashes. In fact, attackers may have already decrypted the passwords, and they may also have users' passwords and email addresses. "Although the data which has been released so far does not include associated email addresses, it is reasonable to assume that such information may be in the hands of the criminals," said Graham Cluley, senior technology consultant at Sophos, in a blog post.

The Computer Emergency Response Team of Finland (CERT-FI) Wednesday warned that many more than the 6,458,020 uploaded password hashes are likely to have been obtained by attackers. "Not all LinkedIn passwords have been published, but it is likely that an attacker is in possession of the rest of the passwords," it said.

According to LinkedIn, as of March 31, 2012, it had 161 million members.

CERT-FI also advised anyone who had reused their LinkedIn password on another site to immediately change it there as well, since it will be at risk of being hacked by anyone who downloads and reverses the uploaded LinkedIn password hashes.

More and more organizations are considering development of an in-house threat intelligence program, dedicating staff and other resources to deep inspection and correlation of network and application data and activity. In our Threat Intelligence: What You Really Need to Know report, we examine the drivers for implementing an in-house threat intelligence program, the issues around staffing and costs, and the tools necessary to do the job effectively. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
GR8Day
50%
50%
GR8Day,
User Rank: Apprentice
6/7/2012 | 3:31:25 PM
re: LinkedIn Users: Change Password Now
I am surprised a social networks who is geared for the professional would not be more security conscious. I am a member and would like to see them take some steps to provide me with additional layers of protection for access to my account verification without unreasonable complexity. It would be great to see them just as some of the other leading companies in their respective verticals giving us the perfect balance between security and user experience by moving to the use of 2FA (two-factor authentication) mobile or other, as a form of a token where the user is asked to telesign into their account by entering a one-time PIN code which is delivered to your phone via SMS or voice. I wish really wish more organizations would start implementing 2FA.
Number 6
50%
50%
Number 6,
User Rank: Apprentice
6/6/2012 | 6:18:22 PM
re: LinkedIn Users: Change Password Now
Nice of LinkedIn to not mention this to their users when they sign on (so far).
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32615
PUBLISHED: 2021-05-13
Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection.
CVE-2021-33026
PUBLISHED: 2021-05-13
The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the ca...
CVE-2021-31876
PUBLISHED: 2021-05-13
Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with ...
CVE-2019-10062
PUBLISHED: 2021-05-13
The HTMLSanitizer class in html-sanitizer.ts in all released versions of the Aurelia framework 1.x repository is vulnerable to XSS. The sanitizer only attempts to filter SCRIPT elements, which makes it feasible for remote attackers to conduct XSS attacks via (for example) JavaScript code in an attri...
CVE-2020-23995
PUBLISHED: 2021-05-13
An information disclosure vulnerability in ILIAS before 5.3.19, 5.4.12 and 6.0 allows remote authenticated attackers to get the upload data path via a workspace upload.