LastPass security incident

Compromise of a DevOps engineer's home computer via keylogger, captured master password; two-stage intrusion (Aug dev environment, then Nov/Dec cloud storage). Encrypted password vaults for all customers stolen.

Last modified

Summary

  • Environment: Password manager
  • Operational impact: Encrypted password vaults for all customers stolen
  • Financial impact: $8.2 million U.S. settlement fund plus a separate crypto-loss pool capped at $16.25 million
  • Record status: Developing record. Reviewed November 2, 2026; updated as evidence emerges.

What happened

In 2022, LastPass experienced an incident in its password manager environment. The retained source describes the attack path as follows: Compromise of a DevOps engineer’s home computer via keylogger, captured master password; two-stage intrusion (Aug dev environment, then Nov/Dec cloud storage). [3]

The documented consequence was: Encrypted password vaults for all customers stolen. [3]

Impact

  • Documented impact: Encrypted password vaults for all customers stolen. [3] The official U.S. settlement administrator describes an $8.2 million settlement fund and a separate cryptocurrency-loss pool capped at $16.25 million. Benefits depend on claims review and allocation; these provisions are not a total loss estimate or confirmation that payments have been made. [2]

Timeline

  1. Canadian settlement approved

    The Supreme Court of British Columbia approved the separate Canadian proceeding, action S-230956.

    [4]
  2. Final settlement approval reported

    The official administrator reports that the court granted final approval of the U.S. settlement for the 2022 incident.

    [2]
  3. Briefing updated

    This briefing was last reviewed and updated on November 2, 2026.

Threat Group & Attack Vector

The retained source describes the attack path as follows: Compromise of a DevOps engineer’s home computer via keylogger, captured master password; two-stage intrusion (Aug dev environment, then Nov/Dec cloud storage). The canonical record does not add intrusion steps beyond those supported by the source. [3]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

The official settlement site reports final approval on September 30, 2026 and says further administration updates will be posted there. This update does not establish completed payments or a court finding of liability. [2]

A separate Canadian settlement for Canadian-resident users affected by the 2022 incident received British Columbia court approval on February 18, 2026. It provides US$3 million before fees and expenses, with distribution subject to approved claims and allocation. Its claims deadline was June 23, 2026. This fund is separate from the U.S. settlement; the reviewed materials do not confirm that Canadian payments have begun. [1][4]