According to a blog report at Ethereum, on December 16, Ethereum staff were made aware that someone had recently gained unauthorized access to a database from forum.ethereum.org and immediately launched a thorough investigation to determine the origin, nature, and scope of this incident.
Here is what they know:
- The information that was recently accessed is a database backup from April 2016 and contained information about 16.5k forum users.
- The leaked information includes
- Messages, both public and private
- Username and email addresses
- Profile information
- Hashed passwords
- ~13k bcrypt hashes (salted)
- ~1.5k WordPress-hashes (salted)
- ~2k accounts without passwords (used federated login)
- The attacker self-disclosed that they are the same person/persons who recently hacked Bo Shen.
- The attacker used social engineering to gain access to a mobile phone number that allowed them to gain access to other accounts, one of which had access to an old database backup from the forum.
They are taking the following steps:
- Forum users whose information may have been compromised by the leak will be receiving an email with additional information.
- They have closed the unauthorized access points involved in the leak.
- They are enforcing stricter security guidelines internally such as removing the recovery phone numbers from accounts and using encryption for sensitive data.
- They are providing the email addresses that they believe were leaked to https://haveibeenpwned.com, a service that helps communicate with affected users.
- They are resetting all forum passwords, effective immediately.
If you you’re affected by the attack they recommend you do the following:
- Ensure that your passwords are not reused between services. If you have reused your forum.ethereum.org password elsewhere, change it in those places.
Additionally, they recommend this excellent blog post by Kraken that provides useful information about how to protect against these types of attacks.
They deeply regret that this incident occurred and are working diligently internally, as well as with external partners to address the incident.
Questions can be directed to [email protected]