After EOSBet broke the security vulnerability of hackers using counterfeit currency bets to win real coins, at 2 o'clock in the afternoon, EOS contract account oo1122334455 issued a token named "EOS", and allocated one billion fake EOS tokens to EOS accounts in full dapphub12345, and then transfer the fake tokens to the account iambillgates (the account that carried out the attack) from this account. After the attacking account used a small fake EOS to verify the attack, a large-scale attack was carried out from 14:31:34 to 14:45:41. There were 11,800 fake EOS listing orders to buy BLACK, IQ, and ADD, and all of them were traded.ExpandCollapse
After EOSBet broke the security vulnerability of hackers using counterfeit currency bets to win real coins, at 2 o'clock in the afternoon, EOS contract account oo1122334455 issued a token named "EOS", and allocated one billion fake EOS tokens to EOS accounts in full dapphub12345, and then transfer the fake tokens to the account iambillgates (the account that carried out the attack) from this account. After the attacking account used a small fake EOS to verify the attack, a large-scale attack was carried out from 14:31:34 to 14:45:41. There were 11,800 fake EOS listing orders to buy BLACK, IQ, and ADD, and all of them were traded.
- Amount of loss
- 11,803 EOS
- Attack method
- Fake EOS Vulnerability Attack
EOS EcosystemSecurity