120 hack event(s)
Description of the event: Attacked by the attacker, the specific content is unknown.
Amount of loss: 200 EOS Attack method: Unknown
Description of the event: Random number was cracked by attacker.
Amount of loss: 2,545 EOS Attack method: Random number attack
Description of the event: EOSeven was transferred 600 million SVN from eosevendice2 to account tuningfinish, then back 450 million to eosevendice2. After that, tuningfinish sold the SVN token on Newdex and finally transferred the resulting EOS to Binance Exchange.
Amount of loss: - Attack method: Insider Manipulation
Description of the event: The hacker "refundwallet" tried to attack the EOSCast game contract "eoscastdmgb1". The hacker first used the "fake EOS" attack method to conduct 8 transfer attacks, but failed, and then successfully attacked 9 times by using the "fake EOS transfer variant". According to the rules of the game, hackers launched attacks with 100, 1,000, and 10,000 fake EOS. Each attack can get 198, 9,800, 19,600 EOS. When the last attack was carried out, the game party noticed an abnormal attack and transferred it in time. After leaving the remaining 8,000 EOS in the bonus pool, in the end, the hacker made a total of 72,912 EOS.
Amount of loss: 70,000 EOS Attack method: Fake EOS Vulnerability Attack
Description of the event: The official forgot to put the seed into the database when expanding the server, and no longer record the seed after the 868590 game.
Amount of loss: 1374.375 EOS Attack method: Operational Mistake
Description of the event: Vulnerability of the random number generator, the attacker can try to calculate the future number of random number generator algorithms by using the information of the previous block and stolen $60,000 from the EosRoyale wallet.
Amount of loss: 11,000 EOS Attack method: Random number attack
Description of the event: RatingToken, a third-party big data platform owned by Cheetah, has detected that DAPP World Conquest developed based on EOS was hacked. Subsequently, the official issued an announcement on its Discord to confirm the fact of the attack. The hacker used the tax payment rules of the game to reject subsequent buyers, which led to the abnormal end of the game. The hacker took all the EOS in the fund pool, and only 0.0155 EOS was left in the contract.
Amount of loss: 4,555 EOS Attack method: Rule Exploitation
Description of the event: The attacker exploited the vulnerabilities in the EOSBet contract to falsify the transfer prompt.
Amount of loss: 145,321 EOS Attack method: Transfer error prompt
Description of the event: The owner permission of the contract account had been modified, after that, 18,000 EOS was transferred to the EOS account fuzl4ta23d1a.
Amount of loss: 18,000 EOS Attack method: Permission Stolen
Description of the event: 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
Description of the event: The attacker exchanged true EOS token with fake token within the vulnerability in the code,winning without betting
Amount of loss: 4,000 EOS Attack method: Code Vulnerability
Description of the event: The game contract does not check the transfer action must initiated by eosio.token or token contract of the game itself.
Amount of loss: - Attack method: Contract Vulnerability
Description of the event: the attacker exchanged true EOS token with fake token within the vulnerability in the code, winning without betting.
Amount of loss: 42,000 EOS Attack method: Code Vulnerability
Description of the event: Because of its random algorithm associated with the time, the same bet will yield different results at different times. Hackers use this feature to reject failed lottery results.
Amount of loss: 4,000 EOS Attack method: Replay attack
Description of the event: The attacker uses the replay attack to obtain multiple winnings in one go.
Amount of loss: 5,000 EOS Attack method: Replay attack
Description of the event: The law of the random number generated by DEOSBET was cracked by hackers.
Amount of loss: 4,000 EOS Attack method: Random number attack
Description of the event: On September 2, 2018, the EOS WIN random number was cracked and 2000 EOS was lost, this attack was not disclosed to the public.
Amount of loss: 2,000 EOS Attack method: Random number attack
Description of the event: The law of the random number generated by Lucky's rock-paper-scissors game was cracked by hackers, and the attacker won the prize by continuing to use rock at the specified time, which has a 38% chance of winning.
Amount of loss: - Attack method: Random number attack
Description of the event: RAM was swallowed up by the malicious contract, and the game party failed to check the caller of transfer action, which led to the exchange of real token with fake token and "Transfer Error Prompt" vulnerability
Amount of loss: - Attack method: Fake Transfer Notification
Description of the event: The EOS Fomo3D game contract suffered an overflow attack and the cash pooling became negative.
Amount of loss: 60,686 EOS Attack method: Overflow vulnerability