- The TRU token plunged from $0.1659 to nearly zero, wiping out its market value.
- Liquidity on decentralized exchanges dried up after the exploit.
- The attacking wallet was linked to a Sparkle protocol attack 12 days earlier.
A serious security breach at the Truebit Protocol caused one of the sharpest collapses seen in decentralized finance this year.
The blockchain project, which focuses on verifiable computation, lost roughly $26.5 million after an attacker exploited a weakness in its smart contract system.
The incident drove the protocol’s native token, TRU, down to almost zero and left liquidity on decentralized exchanges severely depleted.
On-chain movements after the exploit reveal how quickly funds were siphoned off, highlighting persistent risks in smart contract design and monitoring across the DeFi sector.
How the exploit unfolded
The breach was first flagged by blockchain security firm PeckShield, which detected a series of suspicious transactions on the Ethereum network.
Analysis showed the attacker drained nearly 8,500 ETH from the Truebit Protocol.
At the time of the exploit, the stolen cryptocurrency was valued at approximately $26.5 million.
On-chain data indicate the funds were quickly split and sent to two different wallet addresses, identified as 0x2735…cE850a and 0xD12f…031a60.
Splitting funds in this manner is a common tactic to complicate tracking and reduce the chances of recovery.
PeckShield’s preliminary findings suggest the exploit targeted a flaw in the protocol’s contract structure, although a detailed technical breakdown has not yet been released.
Token collapse and liquidity shock
The market impact was immediate. Truebit’s native TRU token plunged from a daily high of $0.1659 to a low of $0.000000018.
The drop effectively erased the token’s market capitalization within hours.
Liquidity on decentralized exchanges also evaporated almost instantly.
With funds stripped and confidence shaken, many token holders were unable to exit positions.
The episode underlined how closely token valuations are tied to protocol security, particularly for smaller DeFi projects where trust can vanish quickly once a vulnerability is confirmed.
Protocol response and containment
Following the breach, the Truebit Protocol issued an official update acknowledging the incident.
The team confirmed that a specific smart contract had been compromised and warned users not to interact with it until further notice.
The protocol stated it is cooperating with law enforcement and taking steps to limit additional damage.
Users were advised to rely only on official communication channels for updates as investigations continue.
No timeline has been shared yet for remediation or any potential recovery efforts.
Link to a prior DeFi attack
PeckShield also reported that the wallet involved in the Truebit exploit had been connected to a separate attack on the Sparkle protocol roughly 12 days earlier.
In that incident, the attacker acquired tokens and then routed funds through Tornado Cash, a privacy service often used to obscure transaction traces.
The repeated use of similar techniques points to an experienced exploiter actively seeking vulnerabilities.
The connection has raised broader concerns across the DeFi ecosystem, where a series of related attacks can amplify perceived risk beyond the directly affected projects.