Block Matrix
Menu

sBOLD vault exploit: share accounting and an eight-minute MEV contest

In reporting published on November 19, 2026, K3 Capital’s Ethereum sBOLD savings vault was described as having lost approximately $3.4 million in liquidity through 97 transactions over about eight minutes. The reported average was roughly $425,000 per minute.

How the vault accounting was exploited

sBOLD is a yield-bearing vault built around BOLD, the stablecoin associated with Liquity. According to Bitquery’s transaction reconstruction, the attacker exploited how the vault accounted for assets transferred into it when calculating the value of an sBOLD share.

Within a transaction, the attacker repeatedly deposited BOLD, introduced wrapped ether (WETH) that was not accounted for on the vault’s balance sheet, and exchanged it internally for BOLD. Bitquery’s account says this inflated the redemption value of sBOLD shares, allowing withdrawals at an overstated valuation at other depositors’ expense.

sBOLD vault exploit: share accounting and an eight-minute MEV contest (1)

What the reported fund flows show

Bitquery reported that, after the original attacker broadcast a withdrawal transaction to the mempool, an automated bot copied and changed its parameters to get ahead of it. The bot extracted approximately $1.91 million—56.18% of the reported $3.4 million total—but paid about $1.78 million for priority inclusion through a block-builder payment channel. That left it roughly $130,000, or 6.81% of the amount it extracted.

The report says Titan built most of the blocks containing the bot’s transactions, while BuilderNet, Ultrasound and Quasar also participated in ordering related blocks. The $1.78 million was gross revenue received by builders, not necessarily their profit: builders still had to bid for blocks through MEV-Boost. The original attacker and an initial funding wallet were reported to have made approximately $520,000 in net proceeds. These figures describe different recipients and accounting measures; they should not be read as a complete reconciliation of every dollar withdrawn.

sBOLD vault exploit: share accounting and an eight-minute MEV contest (2)

Audit warning and response

ChainSecurity completed a code audit of sBOLD in May 2025 and warned of a path to extract excess value through self-liquidation. At the time of the November 19 report, parties were still checking whether this attack used that mechanism; the earlier warning does not, by itself, establish a match.

The report identified restrictions on non-allowlisted token transfers, per-block redemption limits and time-weighted oracles as potential defenses for ERC-4626 vaults, not as measures confirmed to be in place. It also said the team was working with tracing organizations to monitor cross-chain fund movements while assessing depositor losses and repairing the vault code.