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

5/19/2016
08:45 AM
100%
0%

LinkedIn: More Than 100 Million Member Accounts Exposed In 2012 Breach

LinkedIn data theft is likely to be much worse than expected with additional data being released now.

The ghost of the past has come back to haunt LinkedIn: the 2012 data breach that led to an unauthorized release of member details is now rearing its head again with an additional set of member data exposed. LinkedIn announced that it's now invalidating the hacked passwords and alerting those members to reset their passwords.

The social media site yesterday clarified that the additional data released from the 2012 breach was likely to be the “email and hashed password combinations of more than 100 million LinkedIn members from that same theft in 2012.” 

Online magazine Motherboard this week reported that a hacker is trying to sell the account information of 117 million LinkedIn users. Motherboard said the hacker has indicated there are 167 million accounts in the hacked database, of which 117 million have both emails and encrypted passwords. Back in 2012, details of only around 6.5 million accounts were posted online, says Motherboard.

LinkedIn is now invalidating passwords for all accounts not changed before the 2012 breach and trying to identify and block suspicious activity on affected accounts.

For more details, click here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:28:17 AM
Nobody cases LinkedIn hacked
For me, people did not seem to care that LinkedIn was hacked in 2012. It did not bother anybody that their resumes and connections was disposed to others. The only problem is the username password, since we all use those in other sites too. :--)))
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:25:28 AM
Re: Persistant
Agree. I am in the same both. Not in LinkedIn but in other sites, I still user the password I defined 5 years ago :--))
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:24:15 AM
Re: A Timing Puzzlement
That is true. Nobody actually cared that LinkedIn was hacked. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:23:10 AM
Re: Thanks
Yes, it is an old case that we had to remember again. It does not go away.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:22:11 AM
hashed password
 

Hass in one way so there is no encryption/decryption on the hash. For me this is the most secure way to deal with the passwords but if your password is simple has can not protect you.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/23/2016 | 9:12:39 AM
Persistant
This promotes the best practice of users changing their password on a regular basis. I would think that unaware users from 2012 would still be using their original password if there was not a forced change.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/23/2016 | 8:59:17 AM
Re: A Timing Puzzlement
Yes, I believe you are correct.
dieselnerd
50%
50%
dieselnerd,
User Rank: Strategist
5/19/2016 | 12:36:28 PM
A Timing Puzzlement
"LinkedIn is now invalidating passwords for all accounts not changed before the 2012 breach..."

Wouldn't that be not changed after the 2012 breach?

 
Fleety
50%
50%
Fleety,
User Rank: Apprentice
5/19/2016 | 9:33:51 AM
Thanks
Thanks for your post !
How Attackers Infiltrate the Supply Chain & What to Do About It
Shay Nahari, Head of Red-Team Services at CyberArk,  7/16/2019
US Mayors Commit to Just Saying No to Ransomware
Robert Lemos, Contributing Writer,  7/16/2019
The Problem with Proprietary Testing: NSS Labs vs. CrowdStrike
Brian Monkman, Executive Director at NetSecOPEN,  7/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12551
PUBLISHED: 2019-07-22
In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the Memcpy function (provided by the scripting engine) allows an attacker to overwrite arbitrary memory, which could lead to code execution.
CVE-2019-12552
PUBLISHED: 2019-07-22
In SweetScape 010 Editor 9.0.1, an integer overflow during the initialization of variables could allow an attacker to cause a denial of service.
CVE-2019-3414
PUBLISHED: 2019-07-22
All versions up to V1.19.20.02 of ZTE OTCP product are impacted by XSS vulnerability. Due to XSS, when an attacker invokes the security management to obtain the resources of the specified operation code owned by a user, the malicious script code could be transmitted in the parameter. If the front en...
CVE-2019-10102
PUBLISHED: 2019-07-22
tcpdump.org tcpdump 4.9.2 is affected by: CWE-126: Buffer Over-read. The impact is: May expose Saved Frame Pointer, Return Address etc. on stack. The component is: line 234: "ND_PRINT((ndo, "%s", buf));", in function named "print_prefix", in "print-hncp.c". Th...
CVE-2019-10102
PUBLISHED: 2019-07-22
aubio 0.4.8 and earlier is affected by: null pointer. The impact is: crash. The component is: filterbank. The attack vector is: pass invalid arguments to new_aubio_filterbank. The fixed version is: after commit eda95c9c22b4f0b466ae94c4708765eaae6e709e.