K3 sBOLD Vault Drained as Builders Kept Most
Attackers emptied K3 Capital's sBOLD savings vault of about $3.43 million in roughly eight minutes on Wednesday, and on-chain data shows the bots that raced to copy the attack paid most of the money to Ethereum's block builders.
Edited and fact-checked by Stephen Sprague
The vault emptied in eight minutes. The builders kept the toll.
The sBOLD vault emptied in about eight minutes on Wednesday. K3 Capital's savings product held about $3.43 million in BOLD, a dollar stablecoin, and by the end of the drain it held almost nothing, because its own books show reported assets falling from 3,428,803.95 BOLD to 2,000.01 BOLD between 12:25 and 12:34 UTC on November 18. Depositors put money into sBOLD to earn interest, and the interest machinery is what the attackers turned against them.
sBOLD is a vault built to the ERC-4626 standard, so a saver deposits BOLD, receives sBOLD shares, and K3 Capital spreads the deposits across stability pools on Liquity V2, a lending protocol, with the rewards flowing back into the vault. Blockaid raised the alarm at 12:50 UTC, about 25 minutes after the first flagged transaction, and the security firm said attackers flash-loaned wrapped staked ether, self-liquidated a Liquity V2 position into the stability pools, minted cheap sBOLD shares, swapped the collateral and redeemed BOLD that belonged to other depositors. K3 Capital paused the contracts at about 13:05 UTC and said at 13:08 that it was investigating malicious activity involving sBOLD, and Liquity said its V2 protocol wasn't affected, described sBOLD as a vault built and run independently by K3 Capital, and told users not to deposit into sBOLD until further notice.
The copycats took most of what was left, because blockchain analytics firm Bitquery traced 97 transactions across the eight minutes and found that one automated bot copied the attack and extracted $1.91 million, about 56 percent of the stolen funds, across 57 of those transactions. The bot then paid most of its proceeds to Ethereum's block builders, the companies that assemble blocks, so its transactions would be processed ahead of rivals, and builders received about $1.78 million in total while the payment for inclusion in a single block reached 44 ether at the peak of the race. Titan built most of the blocks carrying the bot's transactions, with BuilderNet, Ultrasound and Quasar also processing them, and the wallet that first put the attack on chain and a wallet it funded kept about $520,000 between them.
An audit had already described a version of this door, because ChainSecurity audited sBOLD in May 2025 and identified a high-severity accounting issue in how the vault treated collateral, including a way to extract value through self-liquidations, which the auditors said was mitigated in a later version of the code. CoinDesk reported that it remains unclear whether Wednesday's attack used that mechanism, whether the reviewed fixes were deployed, or whether a different accounting weakness was involved, and K3 Capital has published no loss figure of its own and no restitution plan. Its public record so far is the pause and the investigation statement.
For businesses
Amazon Business is Amazon’s purchasing store for companies, with business accounts and quantity ordering.Register with Amazon BusinessThe check for a saver in any vault like this one is mechanical, because a yield vault is a contract and its share price is an accounting claim rather than a bank balance. The sBOLD drain ran through the share price itself, which is why the money could leave in eight minutes without anyone breaking a lock, and depositors are now waiting on the same party they were trusting before Wednesday. K3 Capital operates the vault, K3 Capital paused it, and K3 Capital's investigation is the only stated path to an answer about what comes back.
The conversation.
Loading comments…
A little more perspective.
Reading is free. Verified members can comment and reply for $2 a month.