1949 hack event(s)
Description of the event: The attacker once again launched an attack on the EOS quiz game eosnowbetext. After preliminary analysis, the attacker still manipulated multiple trumpets to attack the game through transaction squeeze, and has already made a profit.
Amount of loss: 200 EOS Attack method: Transaction congestion attack
Description of the event: According to a report from CoinDesk Korea, the exchange was hacked for a total of 3.1 million EOS, which was withdrawn from the exchange’s “hot” (internet connected) wallet through a series of transactions. Based on the data from CoinMarketCap, EOS is currently trading at $4.22, making the total value of the coins lost around $13 million. The company said in its statement that it suspects the hack was conducted by an insider, since no evidence of external exploit has been found.
Amount of loss: 3,132,672 EOS Attack method: Unknown
Description of the event: According to a report from CoinDesk Korea, Bithumb may have also lost 20.2 million XRP in the recent breach. The XRP was moved from Bithumb’s wallet on March 29 in transactions that can be seen on XRPSCAN.
Amount of loss: 20,172,060 XRP Attack method: Wallet Stolen
Description of the event: The transfer does not determine that to and from cannot be the same address, resulting in an attack that can create more than 15w TCC tokens without foundation.
Amount of loss: 150,000 TCC Attack method: Contract Vulnerability
Description of the event: ZION.games sustained attack by malicious users ggggggggggxx, profits of more than 2849 EOS, and transferred to the Binance Exchange. The attack is similar to the attack on TGON, suspected to be the same group.
Amount of loss: 2,849 EOS Attack method: Roll back attack
Description of the event: The attacker controlled multiple accounts to launch continuously attacks on the TGON, made thousands of EOS in profit from the TGON, and transferred to the Binance Exchange.
Amount of loss: 1,606.8268 EOS Attack method: Roll back attack
Description of the event: BiKi.com announced that at 0:08:23 on March 26, the BiKi.com community received a user feedback that his password has been tampered with and need to bind the new Google verification code.At around 5 in the morning, 28 users had the same problem, and the risk control system received an alarm. After investigation, it is because some users are not bound to Google verification code and third-party verification code service provider SMS is hijacked and caused. At present, the number of of accounts that have been tampered with passwords is 37, and the account involved in asset transfer is 18, and the loss amount is 12.33 million USDT, the BiKi.com will bear the full amount of the loss.
Amount of loss: 123,300 USDT Attack method: unknown
Description of the event: Crypptocurrency expert Nick Schteringard said on Twitter yesterday, that the hacker appears to have stolen roughly $6 million in Coinbene Coin and $39 million in Maximine Coin, which it later dumped on the market.
Amount of loss: $ 45,000,000 Attack method: Unknown
Description of the event: DragonEx announced the news on its official Telegram channel on Monday, stating that, on Sunday, March 24, it had suffered a cyberattack that saw cryptocurrency funds owned by users and the exchange “transferred and stolen.” In updates on the hack today, DragonEx’s Telegram admin provided wallet addresses for 20 cryptocurrencies to which the stolen funds had apparently been transferred. The list included the top five cryptos by market capitalization: bitcoin (BTC), ether (ETH), XRP, litecoin (LTC) and EOS, as well as the tether stablecoin (USDT) for which six destination addresses were provided.
Amount of loss: $ 6,028,283 Attack method: Wallet Stolen
Description of the event: The Etbox platform wallet was hacked, causing the platform’s digital assets to be stolen.
Amount of loss: $ 132,000 Attack method: Unknown
Description of the event: The attacker launch continuously attacks and profit from the dBet Games.
Amount of loss: 24.8 EOS Attack method: Transaction congestion attack
Description of the event: The attacker justjiezhan1 launched an attack on the EOS game "cubecontract" and has already made a profit. Prior to this, the attacker justjiezhan1 started deploying the attack contract at around 12:00:41 on the same day. The analysts preliminary analyzed that the attacker was, still the same as the previous attack mean, transaction congestion attack.
Amount of loss: 49.6 EOS Attack method: Transaction congestion attack
Description of the event: The attacker launched continuously attacks and profit from the EOSVegas. The analysis found that the attack mean used by the attacker was transaction congestion attack. The account is extremely active. It just attacked the quiz game EOS Cube and its related account has been marked as high risk.
Amount of loss: 39 EOS Attack method: Transaction congestion attack
Description of the event: The attacker launched a hard_fail attack on the exchange and profited thousands of EOS.
Amount of loss: - Attack method: Hard_fail attack
Description of the event: The attacker justjiezhan1 launched an attack on the EOS game "YUM.games" and has already made a profit. After analysis, it is suspected that the attacker calls "gamestart" and draws the prize directly without betting the game.
Amount of loss: 113 EOS Attack method: Contract Vulnerability
Description of the event: The attacker launched continuously attacks on the LuckyGo, profiting hundreds of EOS.
Amount of loss: 200 EOS Attack method: Transaction congestion attack
Description of the event: The attacker launched continuously attacks on the dBet Games, profiting hundreds of EUSD which stablecoins issued on EOS. And has sold through the decentralized exchange Newdex.
Amount of loss: 685 EUSD Attack method: Transaction congestion attack
Description of the event: The attacker launched continuous attacks on EOS DApp nkpaymentcap and successfully profited 50,000 EOS. After analysis, it was found that the attacker used a fake transfer notification attack to obtain a large number of contract tokens, and then exchanged the tokens into real EOS for cash out through the DApp contract.
Amount of loss: 50,000 EOS Attack method: Transfer error prompt
Description of the event: The attacker launched a continuous attack on the EOS quiz game Vegas Town, profited thousands of EOS, and has been transferred to the ZB exchange. Preliminary analysis found that hackers used the failed (hard_fail) transfer transaction to cheat the game server, resulting in continued awards.
Amount of loss: 2,219 EOS Attack method: Hard_fail attack
Description of the event: The attacker launched a continuous attack on the EOS quiz game Gamble EOS, successfully profited thousands of EOS, and has been transferred to the Huobi exchange. After analysis, it was found that the attack method used by the attacker was a false transfer notification.
Amount of loss: 2,043.6 EOS Attack method: Transfer error prompt