How do you know if your LinkedIn password has been hacked?

After the recent breach of over 1.5 million LinkedIn password hack, you must be worried that your password might have been compromised. No wonder there are people who wants to make it sure.

Good news is that there is a tool which can help you to accomplish the task. Password management firm LastPass has released a secure tool to see if your password was among the stolen one.

It has been now officially confirmed that there has been breach in eHarmony security from LinkedIn and eHarmony representatives.

Whether your account has been hacked or not, you should definitely change your password immediately to make sure you doesn't get on the dumb list. You must already has been using the "change password" cycle every month for your individual accounts.

SEE ALSO : 4 Tips to protect your Social Account from hackers

Although usernames associated with the passwords were not released, the passwords themselves will surely be used to help reverse-engineer other cryptography systems. We also expect to see these passwords added to dictionary lists of programs that attempt to break into various accounts.

 

So, how do you actually check your account password against the recent the recent LinkedIn breach? here's how --

 

After typing your LinkedIn password into LastPass's tool, the service computes its SHA-1 hash and sends the result to LastPass.com. It then searches the list of 6.5 million leaked password hashes.

"All that's communicated to LastPass is the hash — the result of the one-way function performed on the password that a user enters in that box," said a LastPass spokesperson. "So let's say you enter 'password1.' You enter it and the tool performs the hashing algorithm. The hash is then sent to LastPass, and if a match is found in the database (of the 6.46 million leaked hashes) on our end, we report back a message saying that your password was compromised."
The spokesperson also noted that the hashes are not stored on its servers: "We don't store the hash on our end. We only perform the check and then delete it."