EOS account security risk: How the attack happens and how to defend it?

Home » News » EOS account security risk: How the attack happens and how to defend it?
July 17, 2018 by
EOS account security risk: How the attack happens and how to defend it?

Slow-moving haze protection team warns of EOS account security risk. The team discussed that the EOS budget programmer strictly courts the node confirmation (at the very least 15 verification nodes) to inform the user that an account has actually been efficiently developed. If it not correctly judged after that a phony account attack might happen.

How does the attack take place?

The assault could happen when an individual makes use of an EOS wallet to sign up an account and the budget prompts that the enrollment achieves success, but the judgment is not strict, the account significance is not registered yet. Customer utilize the account to take out money from a transaction. If any kind of part of the procedure is harmful, it may trigger the customer to take out from an account that is not his own.

See also: Did EOS attack Ethereum blockchain? Dan Larimer responds

How to defend against the attack?

Survey the node and return the irreversible block info and after that motivate the success. The details technical procedure consists of: push_transaction to get trx_id, request user interface BLOG POST/ v1/history/get _ transaction and in the return parameter, block_num is less than or equal to last_irreversible_block, which is irreversible.

Recently, a blockchain safety business, PeckShield just recently evaluated the safety and security of EOS accounts and also found that some users were making use of a secret key to severe security threats. The located that the primary reason for the problem is that the part of the secret key generation tool enables the customers to use a weak mnemonic mix. And, the secret trick that’s produced by doing this is extra vulnerable to “rainbow” assaults. It could even lead to the burglary of electronic possessions.

See also: How to lower the cost of EOS RAM? Dan Larimer shares a three-step plan

PeckShield composed, “The essence of the risk is caused by an inappropriate use third-party EOS key-pair generation tools, consisting of yet not restricted to EOSTEA. With user-provided seeds, these devices substantially assist in users to produce their EOS key sets.”

They likewise included a solution saying, “… if an easy seed is chosen (by the customer) and permitted (by the tool), the generated secrets might be exposed and also manipulated by introducing the rainbow table attack (or dictionary strike).” They pointed out in their blog that in order to secure affected holders, PeckShield will be releasing a public service known as EOSRescuer.

Leave a Reply

Your email address will not be published. Required fields are marked *

© Copyright 2018. Befinex. Designed by Space-Themes.com.