For builders, the question in the sBOLD vault attack is how a deposit could change the value assigned to a vault share—and let someone redeem more than they should. In its November 19, 2026 report, Deep Tide TechFlow said K3 Capital’s Ethereum-based sBOLD savings vault lost about $3.4 million in an attack involving 97 transactions over roughly eight minutes.
The reported accounting failure
sBOLD is a yield-bearing vault built around BOLD, the stablecoin of the Liquity protocol. Citing Bitquery’s transaction analysis, the report said the attacker repeatedly deposited BOLD, introduced wrapped ether (WETH) that was not counted on the vault’s balance sheet, and swapped it internally for BOLD. This reportedly inflated the redemption value of each sBOLD share, allowing withdrawals against value belonging to other depositors.

A bot captured part of the withdrawal
According to the report, an automated maximal extractable value (MEV) bot detected the original attacker’s transaction in the mempool, copied and changed its parameters, and withdrew about $1.91 million first—56.18% of the reported $3.4 million loss. The bot paid roughly $1.78 million in priority fees to block builders, leaving it about $130,000. The report said the original attacker and the wallet that initially funded the attack ultimately netted about $520,000.
Titan handled most blocks containing the bot’s transactions, the report said; BuilderNet, Ultrasound and Quasar also participated in ordering related blocks. It cautioned that the $1.78 million was gross fee revenue for builders, who still had to bid for block proposals through MEV-Boost.
ChainSecurity audited sBOLD in May 2025 and warned of a path to extract excess value through self-liquidation. The report said investigators were still checking whether that path was used in this attack. It also described restrictions on unapproved token transfers, per-block redemption limits and time-weighted oracles as potential safeguards for ERC-4626 vaults—not protections confirmed to have been in place here. The team was reportedly tracking fund movements, assessing depositor losses and working on a code fix.

