K3 Capital sBOLD vault (November 2026) hack — November 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | November 18, 2026 |
| Target type | Other |
| Loss | $3,420,000Price at time of incident |
| Method | Contract logic errorProvisional: a flaw in how the sBOLD vault valued its assets let attackers mint shares cheaply and redeem them for other depositors' BOLD. Blockaid described flash-loaned wstETH and self-liquidated Liquity V2 troves; Bitquery found no trove liquidated and says the collateral came from WETH the attacker sent to the vault. K3 Capital has not published a root cause |
| Chains | Ethereum |
| Audited beforehand | Yes |
| Outcome | Unresolved |
What happened
On 18 November 2026 sBOLD, a yield vault built and maintained by K3 Capital on top of Liquity V2, was emptied in about eight minutes. sBOLD pools deposits of BOLD, Liquity's dollar stablecoin, and reinvests the returns earned in Liquity's Stability Pools. Bitquery counted 97 drain transactions from six wallets between 12:25:23 and 12:33:35 UTC, taking about $3.42 million, everything the vault held; Blockaid's alert put it at about $3.43 million. K3 Capital said at 13:08 UTC that it was investigating malicious activity involving sBOLD and had paused the contracts.
The mechanism is not settled. Blockaid said the attackers flash-loaned wstETH, self-liquidated a Liquity V2 trove into the Stability Pools, minted cheap sBOLD shares and redeemed other depositors' BOLD. Bitquery found no trove liquidated in the window and says the collateral the vault priced came from WETH the attacker sent to it. Both describe a flaw in how the vault valued its own assets; crypto.news notes that a May 2025 audit of sBOLD had flagged self-liquidation risks.
Most of the money did not stay with whoever found the bug. A copycat MEV bot sent 57 of the 97 transactions and pulled out $1.91 million, and block builders received $1.78 million in priority payments; Bitquery puts the share kept by builders and the bot's payout wallet at 59%. The wallet that first deployed the attack, and a wallet it funded, took about $0.52 million and moved it through THORChain and Maya Protocol toward Bitcoin. Nothing has been reported returned, and K3 Capital has not said how depositors will be treated.
Sources
- K3 Capital on X (18 November 2026, 13:08 UTC)Primary · retrieved 2026-11-20
- Blockaid alert on X (18 November 2026, 12:50 UTC)Secondary · retrieved 2026-11-20
- Bitquery investigation (18 November 2026)Secondary · retrieved 2026-11-20
- crypto.news (18 November 2026)Secondary · retrieved 2026-11-20
- SlowMist Hacked database, K3 Capital entry (18 November 2026)Aggregator · retrieved 2026-11-20
Changes to this entry
- Added at Bitquery's $3.42m count of 97 transactions (Blockaid $3.43m as the high end). Provisional: K3 Capital has published no figure or root cause, and Blockaid's and Bitquery's accounts of the mechanism differ.
Cite this
This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.
iTokenly Hack Registry, "K3 Capital sBOLD vault (November 2026) hack — November 2026", iTokenly, accessed 2026-11-21, https://itokenly.com/hacks/k3-capital-sbold-vault-november-2026https://itokenly.com/hacks/k3-capital-sbold-vault-november-2026Permalinks never change. If an entry is renamed, the old address keeps working.
Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.