{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihma3dsqve64yfy6in5in5d5kubmasn5ok7zlcjov7prr2a43nhje",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mnfdj6uny2a2"
  },
  "path": "/t/brute-force-attack-on-dashlane-user-accounts/38315#post_1",
  "publishedAt": "2026-06-03T14:03:24.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "https://support.dashlane.com/hc/en-us/articles/36038764990866-Security-advisory-Brute-force-attack-on-Dashlane-user-accounts?7194ef805fa2d04b0f7e8c9521f97343",
    "Infosec Exchange – 1 Jun 26",
    "BrianKrebs (@briankrebs@infosec.exchange)"
  ],
  "textContent": "https://support.dashlane.com/hc/en-us/articles/36038764990866-Security-advisory-Brute-force-attack-on-Dashlane-user-accounts?7194ef805fa2d04b0f7e8c9521f97343\n\n> Starting on Sunday, May 31, 2026, an external party launched a brute force attack against certain Dashlane user accounts. The goal of the attack was to brute-force two-factor authentication (2FA) protections to allow the attacker to register new devices on existing user accounts.\n\nBrian Krebs also provides some more information on his Mastodon account.\n\nInfosec Exchange – 1 Jun 26\n\n### BrianKrebs (@briankrebs@infosec.exchange)\n\nDashlane says services are all back up, and that the account weirdness was caused by brute force attacks, \"resulting in the suspension of those accounts as part of Dashlane’s built-in security measures. The affected accounts have now been...",
  "title": "Brute force attack on Dashlane user accounts"
}