Cyvers Flags Suspected $26M Ethereum Loss at Truebit (TRU)
Crypto analytics firm Cyvers flagged a potential incident involving Truebit (TRU) on January 8, after detecting a suspicious Ethereum transaction that could have resulted in a loss of roughly $26 million. On-chain data showed TRU experiencing a staggering one-day drop of 99.95% on at least one token tracker—typically a sign of a DEX liquidity collapse or a broken price feed, rather than normal selling activity.
The transaction in question, labeled “Truebit Protocol: Purchase,” points to Ethereum address 0x764C64b2A09b09Acb100B80d8c505Aa6a0302EF2, which is tagged as a Truebit contract on Etherscan. Cyvers estimates the movement involved 8,535 ETH (around $26 million at ~$3,100 per ETH). Analysts are still trying to determine whether this ETH belonged to Truebit’s treasury, represents a mispriced purchase, or came from a compromised hot wallet tied to TRU sales, which the project documentation notes always transact in ETH.
Before the crash, CoinGecko reported TRU trading at $0.1611, up 4.1% over 24 hours, before it plunged to $0.00007923.
There’s also been historical confusion between Truebit (TRU) and TrueFi (TRU), which can create problems for trading desks that rely solely on ticker symbols. Truebit’s token contract is 0xf65B5C5104c4faFD4b709d9D60a185eAE063276c, but symbol collisions have repeatedly caused errors in execution and risk systems.
From a trading desk perspective, the key takeaway isn’t just that TRU fell 99.95%. The real concern is that this suspicious purchase contract—whether it touched treasury ETH, fee rails, or sales flows—represents potential counterparty risk. Market makers are likely to widen spreads or pull quotes until the situation is clarified and the exact source of the ETH movement is confirmed.
