Ethereum Groups Net $3.4M From Vault Hack, Data Reveals

Ethereum block builders received the most in a $3.4 million vault hack, data shows
More than half of the $3.4 million drained from K3 Capital’s sBOLD savings vault this week flowed to Ethereum block builders, according to onchain data tied to the exploit.
Blockchain analytics firm Bitquery traced 97 transactions that emptied the vault in roughly eight minutes on Wednesday. The firm’s analysis shows bots competing to exploit the same vulnerability routed about $1.78 million in payments to block builders—the companies responsible for assembling transactions into Ethereum blocks.
The $1.78 million figure reflects incoming payments, not confirmed profits. Builders typically share revenue with validators, the computers that check transactions and publish blocks on Ethereum, and the analysis does not establish how much builders ultimately retained.
A review of the transactions found the original attacker and a wallet it funded ended up with roughly $520,000, notably less than the amount paid to builders amid the scramble to get transactions included ahead of rivals.
One automated trading bot copied the exploit and extracted $1.91 million, or about 56% of the stolen funds. However, the bot paid away most of those proceeds to block builders—an illustration of how high-priority transaction inclusion on Ethereum can redirect a large share of exploit value away from the attacker and toward infrastructure participants during fast-moving incidents.
The incident underscores a recurring dynamic in Ethereum’s block production market: when multiple bots race to exploit the same weakness, they may bid aggressively for inclusion, pushing significant sums to block builders and validators even when the underlying event is a theft.
Separately, security firm Cyvers said its real-time monitoring systems detected an anomalous Ethereum transfer in which a single address received around 8,535 ETH, labeled on-chain as “Truebit Protocol: Purchase.” Based on current market prices, Cyvers estimated the transaction value at approximately $26 million.
Cyvers said the activity triggered alerts due to unusual behavior and elevated risk indicators, describing the transfer as inconsistent with typical transaction flows associated with the protocol. As of publication, Truebit had not publicly disclosed any security incident or confirmed a loss, and no official explanation had been provided for the transfer.
It remains unclear whether the funds moved as part of an exploit, an internal operation, or a misconfigured contract interaction. Cyvers said it continues monitoring the address and related transactions for further movement of funds, emphasizing that it did not attribute the activity to a confirmed exploit.
