LinkedIn linkedin.com

LinkedIn data breach: what happened and what to do

LinkedIn was hacked in 2012, and in May 2016 the stolen data was offered for sale. Have I Been Pwned lists about 164.6 million email addresses and passwords, stored as unsalted SHA1 hashes that were quickly cracked.

View all 13,115 breaches
Breach date
5 May 2012
Affected
164,611,595
Data exposed
Email addresses, Passwords
Verified
Yes
Last updated

Source: Have I Been Pwned (CC BY 4.0)

LinkedIn's best-known breach has two dates. The hack happened in 2012. The data surfaced four years later, in May 2016, when a seller offered it online. Both dates matter if you had an account back then.

What happened

In 2012, LinkedIn said some members' passwords had been stolen, forced a password reset on accounts it believed were affected, and told everyone to change their passwords. At the time it put the number of passwords involved at about 6.5 million.

In May 2016 a seller going by the name "Peace" offered a much larger set of email and password combinations for about 5 bitcoin. LinkedIn said it had learned of a further data set from the 2012 theft, invalidated the passwords of affected accounts and contacted those members to reset them. It said it had no indication of a new breach. Have I Been Pwned (HIBP) loaded the data and counts 164,611,595 email addresses.

What was exposed

HIBP lists two things: email addresses and passwords. The passwords were stored as SHA1 hashes without salt. That is a weak setup, because identical passwords produce identical hashes and attackers can crack common ones in bulk. HIBP notes the vast majority were cracked within days of the data being released.

What it lets criminals do

The risk here is credential stuffing: trying a leaked email and password pair on other sites. Because LinkedIn used the same address as the login for many people, and plenty of people reuse passwords, a 2012 password could unlock a different account years later. A cracked password also makes targeted phishing easier, since the attacker can quote something you really used.

An email address alone is mostly a spam and phishing risk. LinkedIn is also a work account, so scam messages that look like recruiter or connection requests are common follow-ups.

The company's response

LinkedIn invalidated the passwords it found in the 2016 set and emailed affected members to reset them.

If you had an account in 2012

You almost certainly changed your password since then. The question is whether you used the same one anywhere else. If you did, and you haven't changed it, fix that now.

Why a 2012 breach still matters

Old password data doesn't expire. Criminals keep large lists of leaked email and password pairs and try them against new targets, so a password you set in 2012 can still be tested on a bank, shop or email account today. The cracked LinkedIn set is one of the most widely circulated of those lists.

Two habits close most of the gap. First, a different password for every site, so one leak can't open the next account. Second, two-factor login on email, since email resets every other account. A password manager makes the first one painless.

Reading the numbers

The figures you'll see vary: 6.5 million, 117 million, 164 million. They refer to different things. The 6.5 million was what LinkedIn confirmed in 2012. The larger figures describe the data that appeared in 2016. HIBP's 164,611,595 counts the unique email addresses it loaded.

What to do if you were in it

  1. 1

    Change any password you shared with LinkedIn

    If you reused your 2012 LinkedIn password on another site, change it there. Use a unique password for every account, with a password manager.

  2. 2

    Turn on two-factor login

    Switch on two-factor authentication on LinkedIn and on your email. An authenticator app or passkey beats text codes.

  3. 3

    Be careful with messages that look like LinkedIn

    Don't click links in emails about connection requests, job offers or account problems. Open the app or type the address yourself.

  4. 4

    Check whether your email or phone is in this and other breaches

    Run a free Serus scan. It checks breach databases for your email, phone and other details and alerts you when they show up in a new leak.

Frequently asked

Was I affected by the LinkedIn breach?

If you had a LinkedIn account in 2012 you may be in the data set. Look up your email on Have I Been Pwned, or run a free Serus scan.

What was exposed in the LinkedIn breach?

Email addresses and passwords. The passwords were unsalted SHA1 hashes, and most were cracked soon after the data was released.

Should I change my password?

Change it if you still use a password from around 2012, or if you used your old LinkedIn password anywhere else.

How many accounts were in the LinkedIn breach?

HIBP counts about 164.6 million email addresses. LinkedIn's 2012 figure of 6.5 million passwords was much smaller than the data that surfaced in 2016.

Sources

Something wrong or out of date? Tell us and we'll re-check it.

Serus

Check if you're exposed in a breach with Serus

Find your leaks. Get alerted to new ones.

Run a free scan

Related guides

All guides

Related articles

All articles

Cookie preferences

Choose which categories we may use. Full details for every cookie are in our Cookie Policy.

Strictly necessary

Authentication, session management, security and fraud prevention, and saving your consent choice. Always active. The site cannot function without them.

Functional

Remember preferences such as language and settings that improve your experience.

Analytics

Help us understand how the site is used, like pages visited, interactions, and performance, so we can improve it.

Marketing & advertising

Measure our marketing and deliver more relevant ads through partners such as Google, Meta, TikTok, X, and Reddit. Used only with your consent.

Your choice is saved for 12 months and applies across serus.ai, including the app. You can change it anytime from the cookie widget or the "Cookie settings" link in the footer. Withdrawing consent does not affect processing that happened before withdrawal.