Dashlane: Investigating Unexpected Account Notifications and Login Issues
Affected components: Email notificationsTwo-factor authentication (2FA)
Timeline of updates
- investigating
We have received reports from several users having received an email that their account has been suspended. We have also received reports that some users are experiencing difficulties in logging in to Dashlane after resetting their master password. We are investigating this situation, and we will provide further updates as soon as we have more information. Thank you for your understanding.
- investigating
We are continuing to investigate the "Account suspended" notifications. Our engineering teams are actively working on a resolution and investigating the root cause of these messages. We are treating this with the highest priority and will provide further updates here as soon as more information becomes available. Thank you for your continued patience and understanding.
- resolved
We can confirm that certain Dashlane user accounts were targeted in a brute force attack by an external party, resulting in the suspension of those accounts as part of Dashlane’s built-in security measures. The affected accounts have now been unsuspended. Our team is actively engaged in this issue and taking measures to address it. There is no evidence of compromise of Dashlane’s systems. Thank you for your patience and understanding.
- monitoring
We can confirm that certain Dashlane user accounts were targeted in a brute force attack by an external party, resulting in the suspension of those accounts as part of Dashlane’s built-in security measures. The affected accounts have now been unsuspended. Our team is actively engaged in this issue and taking measures to address it. There is no evidence of compromise of Dashlane’s systems. Thank you for your patience and understanding.
- monitoring
Dashlane has published a Security Advisory and customer FAQ with additional details of the incident, investigation status, impact to user accounts, and steps we’ve taken to protect customers. There is no evidence that Dashlane’s internal system has been impacted. For further information, please reference our Security Advisory: https://support.dashlane.com/hc/articles/36038764990866 (opens in new tab)
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e29b0d5c13e06bf4…
Impact, status and times are the vendor’s own, as last archived. View on status.dashlane.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Dashlane, started 2026-05-31 15:19 UTC, not resolved, 5 update(s).
- Title
- Investigating Unexpected Account Notifications and Login Issues
- Vendor
- Dashlane
- Date
- URL
- https://rewindex.com/company/dashlane/incidents/6a1c519ceac9dc05ffa1f526
Dashlane profileRecent Dashlane incidentsAll outages on May 31, 2026Dashlane in May 2026MarkdownJSON