Millions of EOS private keys were stolen, will this affect the EOS voting rate?
Today, IMEOS announced that millions of EOS private keys were stolen by hackers, and the exchange delayed the activation of the EOS mainnet. At present, more than 60 victims in the English and Korean regions have been counted, and the victims in the Chinese region have not yet been counted.
EOS42, EOSCannon (Canon Community), EOS New York, EOSNation, BlockSmith, EOSAmsterdam, EOSRio, EOSDAC nodes are working together to retrieve the lost EOS. At present, 3 accounts have been retrieved and one has been claimed.
According to Canon node CTO bean analysis,The EOS theft this time may be due to the fact that when the user copied and pasted the private key, it was monitored by some malicious programs, users are advised not to copy the private key.
IMEOS said that it also tracked related issues yesterday, and some users suspected that their private keys were leaked and operated by others. IMEOS suspects,The loss of the private key may be caused by a security vulnerability on the WEB side。
Coincidentally, just yesterday, 360, which discovered the EOS security vulnerability, published an article stating that the 360 Security Center has recently monitored that the "clipboard ghost" Trojan horse is very active. The Trojan horse constantly monitors the user's clipboard content to determine whether it is a virtual currency address. And when the user trades, the target address is changed to his own address.
Currently, EOS is on the key nodes that enable voting on the mainnet. Yesterday, the sluggish voting rate showed a tendency to recover, reaching 8.4255%, but today there was a sudden loss of the EOS private key. Is it possible that it will affect the activation of voting on the EOS mainnet?
reasonreasonimage description
(EOS voting method, source: AntPool)
In addition, some wallets that support EOS voting have also been exposed to a large number of vulnerabilities, using an insufficiently secure random number algorithm in the signature code, resulting in repeated k values during the signature transaction process, which may lead to exposure of the private key. The option of voting on behalf of exchanges also brings concerns about unfairness in voting.
The theft of millions of EOS has made the concerns of users who are worried about the security of their private keys a reality. Voting is not profitable for users, and they still need to take the risk of being stolen. In this way, it will only dampen users' willingness to vote, and it may be more difficult to promote the launch of the EOS mainnet, which will hurt the EOS community self-evidently.
Whether it's developing new software or changing voting rules, addressing security issues is imperative.
(I am Mo Xinnan, the author of Odaily. I am exploring the real blockchain. If you are looking for reports, please add WeChat: 16601131135. Please note your name, company, and position.)
(I am Mo Xinnan, the author of Odaily. I am exploring the real blockchain. If you are looking for reports, please add WeChat: 16601131135. Please note your name, company, and position.)
