LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Ethereum Data Breach (2016)

HIGH severityConfirmedHow we verify

Ethereum Data Breach (2016): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·December 16, 2016

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Ethereum Data Breach (2016)

Reported December 16, 2016. Approximately 16K people affected.

HIGH
Severity
16K
People affected
6
Data types exposed
December 16, 2016
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Ethereum Data Breach (2016) (reported December 16, 2016) exposed Email addresses, IP addresses, Passwords and Private messages belonging to roughly 16K people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
HIGH severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Ethereum Data Breach (2016) breach?
16K accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

In December 2016, the forum associated with the Ethereum blockchain platform reported a data breach that exposed information linked to approximately 16,000 user accounts. The incident involved a database containing email addresses, IP addresses, usernames, private messages, website activity records, and passwords that were stored mostly as bcrypt hashes. Ethereum itself submitted a list of the affected email addresses to the Have I Been Pwned service, confirming the exposure without providing further technical details on how access was obtained. The breach was made public on 16 December 2016. No additional information has been released about the precise timing of the intrusion, the method used to gain entry, or any subsequent actions taken by the organization beyond the self-submission of email addresses.

Breaking down the breach

The available facts are limited to the reported date, the approximate number of affected accounts, and the categories of data contained in the forum database. The organization stated that the database held over 16,000 unique email addresses together with IP addresses, private forum messages, and mostly bcrypt-hashed passwords. No further breakdown of file counts, exact dates of access, or technical indicators has been disclosed publicly.

How a breach like this happens

Forum databases are frequently targeted because they store user credentials and communication records in a single location. Typical incidents of this kind involve unauthorized access through vulnerabilities in web applications, weak authentication controls, or compromised administrative accounts. Once inside, an attacker can copy tables containing email addresses, hashed passwords, and message logs. Organizations sometimes discover such events only after the data appears elsewhere or after routine security reviews.

Who is Ethereum?

Ethereum operates a public blockchain platform that supports decentralized applications and smart contracts. Its associated forum served as a discussion space for developers, users, and participants in the Ethereum ecosystem. A breach at this site is consequential because forum accounts often link to cryptocurrency wallets, project contributions, and technical discussions that can reveal patterns of activity or contact details used elsewhere.

What data was at risk

The breach record lists the following data types as present in the exposed database: email addresses, IP addresses, passwords, private messages, usernames, and website activity. Passwords were stored mostly as bcrypt hashes. No confirmation has been provided on whether additional fields, such as wallet addresses or full message contents, were included beyond the categories already named.

The real-world impact

Individuals whose email addresses and usernames appeared in the data may receive targeted phishing attempts that reference their Ethereum forum activity. Hashed passwords reduce immediate risk if they remain unbroken, yet any reused credentials could still be tested against other services. IP addresses and message logs can contribute to profiling of online behavior, though the concrete effects depend on how the data is later used or combined with other sources.

What to do if you're exposed

Review any Ethereum forum account you maintained and change its password if the service remains active. Enable two-factor authentication on linked accounts and avoid reusing the exposed password elsewhere. Monitor incoming email for unsolicited messages that reference the forum. Readers can also run a free exposure scan of their email address against known breach data to check for appearances in this or other incidents.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyEthereum security record
74/100
DoxxScan™ · Moderate doxx risk
B- 78Above-average record

1 reported incident on record.

See Ethereum’s full breach history →

More recent breaches

Anti Public Combo List Data Breach (2016)December 16, 2016PayAsUGym Data Breach (2016)December 15, 2016MrExcel Data Breach (2016)December 5, 2016Biohack.me Data Breach (2016)December 2, 2016

Latest breaches

Read GalaxyWarden’s full analysis of the Ethereum Data Breach (2016) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram