On 2024-06-23, 00:19 AM UTC, a phishing e mail was despatched out to 35,794 e mail addresses by updates@weblog.ethereum.org with the next content material
Customers who clicked the hyperlink within the e mail had been despatched to a malicious web site:
This web site had a crypto drainer working within the background, and if a consumer initiated their pockets and signed the transaction requested by their web site their pockets would have been drained.
Our inside safety workforce instantly launched an investigation to assist decide who launched the assault, what the intention of the assault was, when it occurred, who was affected, and the way it occurred.
A few of the intial actions taken had been:
- Prevented the risk actor from sending extra emails.
- Despatched out notifications through twitter and e mail to not click on the hyperlink in query.
- Closed down the malicious entry path the risk actor had used to acquire entry into the mailing record supplier.
- Submitted the malicious hyperlink to numerous blacklists, and it was then blocked by majority of web3 pockets suppliers and cloudflare.
Our investigation into the assault confirmed that:
- The risk actor imported a big e mail record of their very own into the mailing record platform for use for the phishing marketing campaign.
- The risk actor exported the weblog mailing record e mail addresses, which was a complete of 3759 e mail addresses.
- Once we in contrast the emails within the e mail record that the risk actor had imported, we may see that the weblog mailing record contained 81 e mail addresses that the risk actor didn’t beforehand have information of, and the remainder had been duplicate addresses.
- Analyzing on-chain transactions made to the risk actor between the time they despatched out the e-mail marketing campaign and the time the malicious area obtained blocked, seem to indicate that no victims misplaced funds throughout this particular marketing campaign despatched by the risk actor.
As we proceed engaged on this incident, now we have taken extra measures equivalent to migrating some mail companies to different suppliers, to additional assist scale back the chance of this occurring once more.
We’re deeply sorry that this incident occurred, and are working diligently with each our inside safety workforce in addition to exterior safety groups to additional assist tackle and examine this incident.
Any questions will be directed to security@ethereum.org.
