Lastpass Security

LastPass Security Response

We Value Your Concerns

Our business is keeping customer information both private and secure.

We appreciate all security concerns brought forth and are constantly striving to keep on top of the latest threats. Being pro-active rather than re-active to emerging security issues is a fundamental belief at LastPass. Every day new security issues and attack vectors are created. LastPass strives to keep abreast on the latest state-of-the-art security developments by working with security researchers and companies. We also work with highly talented members of the LastPass community who offer their expertise to help improve the product for everyone.

If you have discovered a potential security issue with our of our products, we kindly ask you to let us know as soon as possible.

Concerned about the Heartbleed Bug?

Please see our blog post for information on how this impacts LastPass and how we're addressing it.

How To Report Security Issues

When reporting potential issues, please try to be as thorough as possible providing us enough information so that we can recreate your findings.

1. Read the LastPass Security FAQs
Read the LastPass Security FAQs to make sure your concern hasn't already been addressed.

2. Identify The Type of Your Security Concern
We have two types of security reports. Both types will be answered promptly, but it is important that you select the right one in order to receive a timely answer to your issue.

If your security issue affects only your account or yourself, then it is classified as a 'Locally Impacting Security Concern'.

If, on the other hand, your security issue can impact all or many LastPass users, then it is classified as a 'Broadly Impacting Security Concern'.

Reporting Locally Impacting Security Concerns
Submit a new support ticket.

Be sure to select 'I Want To: Report a security issue'.
We'll respond back to you within the support ticket unless the issue is of a sensitive or urgent nature, in which case we'll email you directly.
Please give us 48-72 hours to review your issue in depth.

Reporting Broadly Impacting Security Concerns
Email us directly at security@lastpass.com.
If the information is sensitive, please encrypt it accordingly.

We'll analyze the information you send and if we feel it's genuine we'll respond back to you directly within a few hours.
If you don't hear back from us within 24 hours, and didn't receive a non-delivery-notification for your sent email, then it's likely that we don't have enough information to deem whether you have found a legitimate exploit. Please try resubmitting your findings but make sure you include a code sample and screencast that clearly demonstrates the exploit you have found. If you are using automated tools to find vulnerabilities, please be aware that these tools always report false positives. Most times, it's insufficient to simply find the vulnerability and point us to an FAQ on the subject: you should show us how it can be used to impact user data or our systems. As an example, if you find a clickjacking vulnerability please clearly show us what end user sensitive action the end user can be tricked into performing.

What Happens After I Submit a Security Concern?

Once you have submitted a security concern, here's what we promise to do on our end:

  1. We'll immediately take steps to identify if the concern is a legitimate issue and determine its severity.
  2. If we require more information, we'll contact you directly. Otherwise, we'll try to fix the issue potentially with your assistance. While fixing the issue will generally be completely in short order, deploying the fix to affected customers will be done based on the issue's severity.
  3. Once the issue is fully resolved to both your and our satisfaction, we'll thank you for your discovery.



LastPass Security FAQs

I have LastPass multifactor authentication enabled but LastPass filled my credentials into a site before I entered my multifactor token. Is this a security issue?

To validate your multifactor token, multifactor authentication requires that you have an Internet connection: if you do not pass us a correct multifactor token, LastPass will never release your encrypted data. However, LastPass also has an 'offline mode': it keeps a locally cached encrypted copy of your data on your local device so that you'll still be able to access your data even in the event that you do not have Internet access. When you log in to LastPass we first log you in offline to the locally cached copy of your data and then try to log you in online. As a result, you might experience cases where LastPass fills in credentials before you provide us your LastPass multifactor token. If you want to prevent this behavior, you can take the following steps:

  1. Log into LastPass
  2. Browser - LastPass Icon - Tools - Clear local cache
  3. Logoff LastPass

My Anti-virus Program Has Warned Me that LastPass Is a Virus/Trojan/Suspicious - Should I Be Concerned?

Most modern anti-virus programs today rely on a trust network to determine if a file represents a threat. As a result, despite signing all executable files we distribute using a digital certificate, every time we release a new version of our software it typically results in anti-virus programs flagging it as suspicious until it is distributed to thousands of users and/or until end users update their virus definitions. If you encounter this issue, the please follow the following steps:

  1. Re-download the problematic files from the LastPass Download page.
  2. Upload the suspicious files to Virus Total, a service that will analyze the files using dozens of the industry's top anti-virus engines. Unless the results indicate that several top anti-virus engines believe the files to be infected, it likely they are safe.
  3. Right click on the files and select 'Properties' from the context-menu, and then choose the 'Digital Signatures' tab. Make sure the files have a valid digital signature and have been signed by 'LastPass' and if necessary, view the certificate. This will assure you that the files were created by LastPass and have not been modified by a rogue 3rd party.
  4. If after the above steps you still believe that files are infected or were not created by LastPass, then please contact us at security@lastpass.com


Click here to view a list of security researchers and companies that have contacted us directly to work with us to fix security flaws safely.