K3 Capital said at 13:08 UTC that it was investigating malicious activity involving sBOLD and had paused the related contracts. Its notice gave no loss estimate or timetable for reopening the vault. Blockaid said attackers obtained vault shares cheaply and redeemed them for BOLD held by other depositors.
Bitquery’s later analysis valued the sBOLD loss at $3.42 million and counted 97 transactions across 37 Ethereum blocks. It attributed 57 transactions to one bot, which it said was linked to 56% of the value removed. The drain took place over eight minutes, from 12:25:23 to 12:33:35 UTC, and emptied the vault about 35 minutes before K3 Capital announced the pause. Bitquery traced $1.78 million in payments to Ethereum block builders—about 52% of its loss estimate—and said it found no indication they knew what the bot was doing.
Blockaid and Bitquery differed on the mechanics of the sBOLD exploit. Blockaid’s alert pointed to the liquidation of a borrower’s Liquity trove; Bitquery said its transaction review found no trove liquidations. Liquity’s documentation describes sBOLD as a third-party vault developed and maintained by K3 Capital. It pools BOLD, Liquity V2’s dollar-pegged stablecoin, and reinvests rewards from Stability Pools, where deposited BOLD covers debt when borrowers are liquidated.
Blockaid put the Gonka bridge loss at about $1.05 million across roughly five transactions and said the attack was still underway when it issued the alert. The firm attributed the incident to a change involving the bridge’s Ethereum signing key. The attacker drained stablecoins remaining in the bridge and minted WGNK, the Ethereum version of Gonka’s native GNK, without backing. The combined $4.48 million estimate adds Blockaid’s two dollar figures and assigns no separate value to the newly issued tokens.

Comments (0)
No comments yet. Be the first!