Attackers have taken about $3.43 million from K3 Capital’s sBOLD vault, a yield product that runs on the Liquity V2 lending protocol, blockchain security firm Blockaid said in an alert on X at 12:50 UTC on Wednesday. Blockaid described the exploit as “ongoing” and said the figure covered roughly 34 transactions “so far,” so the total may have grown since the post.
K3 Capital responded on X at 13:08 UTC, about 17 minutes after Blockaid’s alert, saying it was “investigating malicious activity involving sBOLD.” “Contracts have been paused,” the post said. It did not give a loss figure or a cause.
One transaction Blockaid flagged in a follow-up post was recorded on Ethereum at 12:25 UTC, about 25 minutes before the alert went out, according to Unchained’s review of the Etherscan record. That single transaction contained 231 separate token transfers.
Get Unchained’s crypto news in your inbox with the free Unchained Daily newsletter.
What sBOLD Does
sBOLD is a vault built to ERC-4626, the Ethereum standard for tokenized vaults. Users deposit BOLD, Liquity V2’s dollar-pegged stablecoin, and the vault places it in Liquity’s stability pools, reserves of BOLD that pay off the debt of loans being liquidated and receive those loans’ collateral in exchange.
Liquity’s own blog describes sBOLD as a third-party project from K3 Capital rather than part of Liquity’s core protocol. Unlike Liquity V2’s contracts, which cannot be changed, the vault has adjustable parts, including its price oracle and the adapter it uses to swap tokens.
How the Attack Worked
Blockaid said the attackers first took a flash loan, money borrowed and repaid inside one transaction, in wstETH, Lido’s wrapped version of staked ether. They then liquidated their own Liquity V2 trove, the protocol’s term for a borrowing position, sending its debt and collateral into the stability pools.
From there, the attackers “minted cheap sBOLD shares” and “swapped the collateral,” according to Blockaid, before redeeming BOLD that belonged to the vault’s other depositors. Blockaid’s follow-up post listed the address of one of the exploiters, a helper contract, and the address of the drained vault.
Earlier Audit
Security firm ChainSecurity finished an audit of sBOLD on May 19, 2025. Its summary stated that “the possibility of value extraction through self-liquidations has been mitigated.” It is not yet known whether Wednesday’s attack used the same route, and K3 Capital has not said what caused it.
Blockaid’s $3.43 million figure reflects losses as of its 12:50 UTC post, and no final tally has been published. K3 Capital’s post did not say what depositors in the vault can expect.
Related Listen: How North Korea Stole $6.3 Billion From Binance in 20 Minutes
