On January 9th early morning, a previously undisclosed contract deployed by Truebit Protocol was successfully exploited by an attacker, resulting in a loss of 8,535.36 ETH, equivalent to approximately $26.4 million. The security team conducted an in-depth investigation and analysis of the incident.



Attack Process Breakdown

Main attack transaction hash: 0xcd4755645595094a8ab984d0db7e3b4aabde72a5c87c4f176a030629c47fb014

The attacker’s steps are quite clear:

First, call the getPurchasePrice() function to query price information. Then, move to the core vulnerability—call the flawed function 0xa0296215() with a very low msg.value. Since the contract source code is not public, decompilation results show that this function has an arithmetic logic vulnerability, likely due to improper integer truncation. Because of this, the attacker was able to mint a large amount of TRU tokens out of thin air.

Next is the cash-out phase. The attacker uses the burn function to "sell" the minted tokens back to the contract, extracting a large amount of ETH. This process was repeated 4 times, each time increasing the msg.value, ultimately nearly draining the contract’s ETH reserves.

Funds Chain Tracking

Based on on-chain data, the team used blockchain investigation and tracking tools to trace the flow of the stolen funds… (The original text does not provide further details)
ETH-0,31%
TRU-0,82%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 10
  • Repost
  • Share
Comment
0/400
BridgeJumpervip
· 11h ago
Another trap of this old contract, the source code is not even public, yet they dare to put so much money in...
View OriginalReply0
BrokeBeansvip
· 01-11 18:17
Another contract with unreleased source code, and this time it really blew up... $26.4 million just gone, can such a basic bug like integer truncation escape audit?
View OriginalReply0
LiquidationWizardvip
· 01-11 11:45
It's another stunt caused by the source code not being open, it should have been fully open-sourced long ago.
View OriginalReply0
SerumDegenvip
· 01-09 12:03
ngl this is just integer overflow with extra steps... unaudited contracts stay unaudited i guess lmao
Reply0
ForkLibertarianvip
· 01-09 12:01
Damn, another integer truncation... How are there still people falling for this kind of vulnerability?
View OriginalReply0
QuorumVotervip
· 01-09 11:57
Integer truncation has failed again; how can there still be people deploying contracts whose source code isn't even public?
View OriginalReply0
SchrodingerWalletvip
· 01-09 11:50
Another trap with an undisclosed contract, this time $26.4 million just disappeared... The integer truncation bug is just too brutal.
View OriginalReply0
MetaMisfitvip
· 01-09 11:48
It's the fault of the source code not being公开. These days, hiding things actually makes it easier to be figured out.
View OriginalReply0
BlockImpostervip
· 01-09 11:42
Another unpublicized contract failure, how familiar this trick is.
View OriginalReply0
View More
  • Pin

Trade Crypto Anywhere Anytime
qrCode
Scan to download Gate App
Community
  • 简体中文
  • English
  • Tiếng Việt
  • 繁體中文
  • Español
  • Русский
  • Français (Afrique)
  • Português (Portugal)
  • Bahasa Indonesia
  • 日本語
  • بالعربية
  • Українська
  • Português (Brasil)