Partner · Blockchain Life 2026 — Dubai, December 1–2 · 15,000+ attendees from 130+ countriesGet tickets →
LIVE
$62,240▼0.5%
DeFi

K3 Capital Pauses sBOLD After a $3.43M Drain on Its Ethereum Vault

19 Nov 2026by CryptoJazz Admin1 min read31 views
K3 Capital Pauses sBOLD After a $3.43M Drain on Its Ethereum Vault

K3 Capital paused the contracts behind its sBOLD vault on Wednesday, after a security firm flagged an attack that was still running. Blockaid put the amount drained from the Ethereum vault at about $3.43 million in an alert timed 12:50 UTC, counting roughly 34 transactions at that point. K3 Capital replied at 13:08 UTC that it was investigating "malicious activity involving sBOLD" and that contracts had been paused. The vault takes deposits of BOLD, a token designed to hold a value of $1, and spreads them across stability pools on the lending protocol Liquity to earn interest. It is a third-party product; Liquity's own core contracts are not involved.

Two descriptions of the same drain

The two published accounts of how the vault was emptied do not match on the step that mattered. Blockaid, as reported by Unchained, says the attackers took a flash loan in wrapped staked ether, liquidated their own Liquity borrowing position so its debt and collateral landed in the stability pools, minted sBOLD shares cheaply, swapped the collateral and redeemed BOLD belonging to other depositors. CoinDesk's description leaves the self-liquidation out. In its telling the attackers deposited BOLD repeatedly, introduced wrapped ether that the vault's accounting initially ignored, converted that ether into BOLD and redeemed their shares at an inflated value, a sequence that could be run several times inside a single transaction. Both routes end with shares redeemed above what the vault's assets backed, the same pattern that cost Kava Lend 55.2 million KAVA to an inflated deposit. Neither account is a postmortem from K3 Capital, which has published none.

The counts keep moving

Blockaid's figure was a live number taken from an attack in progress. CoinDesk, writing on Thursday morning, puts the total at $3.4 million across 97 transactions traced by the analytics firm Bitquery. The jump from 34 to 97 is a difference of basis, not a contradiction: one count was taken mid-attack, the other after it. On duration the two do split. CoinDesk says the vault was drained in about eight minutes; Unchained's timeline runs from a flagged transaction at 12:25 UTC to Blockaid's 12:50 alert describing the attack as still live, which is closer to half an hour. No final tally has been published.

Who ended up with the money, on one account

The sharpest figures in the story rest on CoinDesk alone, and on its own review of the transactions. It reports that a bot copied the attack and extracted $1.91 million, 56% of the stolen funds, and that competing bots paid approximately $1.78 million to Ethereum block builders to have their transactions ordered first. The original attacker and a wallet it funded were left with about $520,000, by that account. CoinDesk names Titan as the builder that assembled most of the blocks carrying the copycat's transactions, with BuilderNet, Ultrasound and Quasar also processing them, and puts the largest single payment for block inclusion at 44 ETH. The outlet cautions that this measures money paid in, not profit kept, since builders pay validators out of it. A bot has beaten an attacker to the funds before; this one followed the attack in instead.

What the 2025 audit had closed

ChainSecurity finished an audit of sBOLD on 19 May 2025, by Unchained's date. It found a route to extract value through self-liquidations and recorded the matter as settled.

"The possibility of value extraction through self-liquidations has been mitigated," the audit said.

Whether Wednesday's attack used that route is not established. Neither outlet says whether the reviewed fixes were deployed, or whether a different accounting weakness was involved, and the vault has adjustable parts, its price oracle and its token-swap adapter among them, that Liquity's own contracts do not. One syndicated report adds that Reental, a real-estate tokenization platform on Polygon, lost roughly $454,000 the same day in a separate proxy-upgrade incident; that figure stands on a single account. K3 Capital has not said what depositors can expect. No recovery has been reported, and crypto.news said the company did not answer its request for comment.

Read also: Hacken Puts Q3 Losses at $1.18B and Points at Audit Scope

← All news