All Breaches
June 7, 2018 Verified Law enforcement

Estonian Citizens (via Estonian Cybercrime Bureau) Data Breach

The Estonian Citizens (via Estonian Cybercrime Bureau) entry does not represent a customer database confirmed as stolen from one company or from an Estonian government system.

655.2 Thousand
Reported Records
2
Data Types
High
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

2
  • Email addresses
  • Passwords

About This Breach

Dated 7 June 2018, the catalog record documents a credential set obtained by Estonian law enforcement and associated with suspected attempts to access online accounts. It is linked to 655,161 email addresses; the verified data classes are email addresses and passwords.

What this record means

The title is a catalog label. It does not mean that every Estonian citizen was affected, that the Estonian Cybercrime Bureau was breached, or that a particular government database was leaked. The defensible interpretation is that email-and-password combinations obtained by law enforcement could have been used in attempts to access mailboxes, cloud services, cryptocurrency platforms, or other accounts.

Potential impact

Credential sets containing passwords create a material account-takeover risk when passwords are reused. If the same email address and password were used on another service, automated credential-stuffing attempts may succeed. Control of an email account can also provide access to password-reset flows for other services.

Recommended actions

  1. Review passwords used around this period and replace any password that is still active or reused with a strong, unique password.
  2. Enable two-factor authentication, prioritizing email, financial, cloud-storage, and cryptocurrency accounts.
  3. Check recovery addresses, active sessions, and forwarding rules on email accounts.
  4. Use a reputable password manager to generate and store a different password for every service.

Scope note

LeakData does not publish leaked passwords. This page explains the catalog metadata for a law-enforcement credential set and defensive account-security steps; it does not recast the source as a breach of a specific institution.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information