CoinSleuth

sBOLD vault exploit: reported $3.4 million loss and an unresolved audit question

For sBOLD depositors, the immediate concern is how much of the vault’s assets remain recoverable. In its November 19, 2026 report, Deep Tide TechFlow said an attacker drained approximately $3.4 million in liquidity from K3 Capital’s Ethereum sBOLD savings vault through 97 transactions over roughly eight minutes. The report said the team was assessing affected deposits, working on a code fix and tracking the movement of funds.

How the reported exploit worked

sBOLD is a yield-bearing vault built around BOLD, the stablecoin associated with Liquity. Citing transaction analysis by Bitquery, the report said the attacker exploited the vault’s accounting for assets transferred into it. Within transactions, the attacker repeatedly deposited BOLD, introduced wrapped ether (WETH) that was not reflected on the balance sheet, and exchanged it internally for BOLD. This reportedly inflated the redemption value of each sBOLD share, allowing withdrawals at the expense of other depositors.

sBOLD vault exploit: reported $3.4 million loss and an unresolved audit question (1)

Where the proceeds went

According to Bitquery’s tracking as described in the report, an automated bot detected the attacker’s withdrawal transaction in the mempool and submitted a competing transaction. The bot extracted approximately $1.91 million—56.18% of the reported $3.4 million total—but paid about $1.78 million in priority fees to block builders, leaving roughly $130,000. The report said the original attacker and the wallet that initially funded the attack ultimately received about $520,000 in net proceeds.

The $1.78 million was gross fee revenue for builders, not necessarily their profit: builders also bid for block inclusion through MEV-Boost. The report identified Titan as building most of the blocks containing the competing transactions and said BuilderNet, Ultrasound and Quasar also participated in relevant block ordering.

sBOLD vault exploit: reported $3.4 million loss and an unresolved audit question (2)

What remains uncertain

ChainSecurity audited sBOLD’s code in May 2025 and warned of a path for extracting excess value through self-liquidation. The November 19 report said parties were still checking whether that previously identified mechanism was involved in this attack; it did not establish that connection.

The report described restricting transfers of non-allowlisted tokens, limiting redemptions per block and using time-weighted oracles as potential defenses for ERC-4626 vaults. It did not say those measures had been implemented in sBOLD. For depositors, the reported accounting failure is a reminder that a vault share’s displayed redemption value depends on how the vault accounts for assets—not just on who holds the shares.

Further reading