Dashlane Users Locked Out Amid Brute Force Attack

Dashlane Users Locked Out Amid Brute Force Attack

First seen 1 Jun 2026, 14:52 UTC TheregisterFeeds2.FeedburnerBleepingcomputerCybersecuritynewsTechcrunch+6 89% similarity 51.8

Article Content

Browse articles
ThreatCluster

Dashlane, a password management service, faced a series of brute force attacks starting on May 31, 2026, leading to the temporary suspension of multiple user accounts. The attacks involved unauthorized attempts to register new devices using incorrect authentication tokens. Dashlane confirmed that these measures were part of their automated security response to protect user accounts from potential hijacking. Users reported receiving emails about account suspensions and suspicious login attempts from various countries, including Korea and Russia. Although Dashlane restored access to affected accounts by June 1, some users continued to experience login issues and reported unresponsive customer support. The company has stated that there is no evidence of a compromise of their internal systems. Dashlane is monitoring the situation and has implemented additional security measures to protect its users.

Key Points: • Dashlane suspended user accounts due to brute force attacks attempting unauthorized access. • The attacks began on May 31, 2026, with users receiving notifications of suspicious activities. • Dashlane confirmed no internal system compromise, but some users still face login issues.

ThreatCluster AI

Timeline

2026-05-31
Brute force attacks initiated
Dashlane began experiencing brute force attacks targeting user accounts, prompting security measures.
Bleepingcomputer
2026-05-31
User accounts suspended
Affected users received emails about account suspensions due to multiple failed login attempts.
Theregister
2026-06-01
Accounts restored
Dashlane confirmed that all affected accounts were restored after the investigation was completed.
Bleepingcomputer
2026-06-01
Dashlane updates status
Dashlane updated its status page, changing the incident from 'resolved' to 'monitoring' due to ongoing user issues.
Theregister
2026-06-02
Ongoing user issues reported
Despite the resolution announcement, some users continued to report login problems and unresponsive support.
Cybersecuritynews

Community

Browse all →

Tracked Entities in This Story