On December 16, we have been made conscious that somebody had not too long ago gained unauthorized entry to a database from discussion board.ethereum.org. We instantly launched an intensive investigation to find out the origin, nature, and scope of this incident. Here’s what we all know:
- The data that was not too long ago accessed is a database backup from April 2016 and contained details about 16.5k discussion board customers.
- The leaked data contains
- Messages, each private and non-private
- IP-addresses
- Username and e mail addresses
- Profile data
- Hashed passwords
- ~13k bcrypt hashes (salted)
- ~1.5k WordPress-hashes (salted)
- ~2k accounts with out passwords (used federated login)
- The attacker self-disclosed that they’re the identical particular person/individuals who not too long ago hacked Bo Shen.
- The attacker used social engineering to realize entry to a cell phone quantity that allowed them to realize entry to different accounts, one in every of which had entry to an previous database backup from the discussion board.
We’re taking the next steps:
- Discussion board customers whose data might have been compromised by the leak might be receiving an e mail with further data.
- We’ve got closed the unauthorized entry factors concerned within the leak.
- We’re implementing stricter safety tips internally comparable to eradicating the restoration cellphone numbers from accounts and utilizing encryption for delicate knowledge.
- We’re offering the e-mail addresses that we imagine have been leaked to https://haveibeenpwned.com, a service that helps talk with affected customers.
- We’re resetting all discussion board passwords, efficient instantly.
In case you have been affected by the assault we advocate you do the next:
- Make sure that your passwords are usually not reused between companies. If in case you have reused your discussion board.ethereum.org password elsewhere, change it in these locations.
Moreover, we advocate this glorious weblog submit by Kraken that gives helpful details about find out how to shield in opposition to all these assaults.
We deeply remorse that this incident occurred and are working diligently internally, in addition to with exterior companions to handle the incident.
Questions may be directed to safety@ethereum.org.