Sign in
Article On-chain

K3 Capital sBOLD hack: losses and the investigation

A timeline of the sBOLD exploit: K3 Capital paused contracts, while Liquity says V2 is unaffected. Tracking the estimated $3.42M loss and disputed details.

K3 Capital sBOLD hack: losses and the investigation
Иллюстрация CoinLab / AI
Developing storyWe are following events and adding new information. Last updated: November 18, 2026, 4:19 PM ET
Contents
  1. What we know now
  2. How it happened
  3. Timeline
  4. Where the funds went
  5. The response from teams and exchanges
  6. What it means for holders

K3 Capital's sBOLD vault on Ethereum was attacked on November 18, 2026. Bitquery estimates that approximately $3.42 million was drained. K3 Capital confirmed an investigation and paused contracts, but its reviewed statement does not establish a final loss or a compensation plan. This timeline distinguishes project announcements from provisional investigative findings.

What we know now

  • K3 Capital paused sBOLD contracts, announcing the response on November 18 at 8:08 AM ET.
  • Liquity says its core V2 protocol is unaffected and describes sBOLD as an independently operated K3 Capital vault.
  • Bitquery estimates approximately $3.42 million drained. Blockaid's initial estimate was about $3.43 million. These describe the same incident and must not be added together.
  • The reviewed project statements do not confirm completed recovery, compensation or a reopening date.
  • A full K3 Capital post-mortem was not available in the reviewed sources. Investigators disagree on part of the mechanism.

How it happened

sBOLD accepts Liquity V2's BOLD stablecoin and gives depositors vault shares. The value of those shares depends on which assets the software includes in its accounting. An additional yield-management layer can introduce its own risk even when underlying infrastructure continues operating.

Bitquery attributes the exploit to a mismatch between collateral held and the calculated value of shares. WETH collateral below a configured threshold was excluded from the valuation. Participants acquired undervalued shares, converted collateral into BOLD that was counted, then redeemed shares after their calculated value rose. Repeating the sequence extracted value from the vault.

The initial Blockaid alert described a self-liquidation of a loan. Bitquery disputes that element, saying its event review found no such liquidations. That disagreement matters: an early description should not be treated as the final outcome of the investigation.

Bitquery did not verify which source-code version the project had deployed. Its findings do not establish that a particular audit fix was ignored or that responsibility has been assigned to any identified developer.

Timeline

  • November 18, 7:25:23⁠–⁠7:33:35 AM ET. Bitquery reconstructs the main drain as approximately eight minutes and 97 transactions. This is an investigator's reconstruction rather than an incident log released by the project.
  • November 18, 7:50 AM ET. Blockaid announced the exploit. The current text of that initial post estimates roughly $3.43 million across about 34 transactions. Its description of an ongoing attack refers to the state at that alert's publication.
  • November 18, 8:08 AM ET. K3 Capital confirmed the investigation and paused contracts.
  • November 18, 8:59 AM ET. Liquity said V2 was unaffected, asked users not to deposit into sBOLD until further notice and said it was supporting K3.
  • November 18, 12:14 PM ET. Bitquery's onchain snapshot ends. Later balances and transfers require separate verification.

Where the funds went

Bitquery links activity to several wallets and copying bots. Its listed addresses include the vault, 0x50bd66d59911f5e086ec87ae43c811e0d059dd11, and a wallet associated with deploying attack code, 0xdc0e2fdeb89d2f363f2ea1b50e923d464c414daa. Those labels describe observed roles, not the established identities of their controllers.

The researchers traced some transfers into THORChain and Maya Protocol. Entering a cross-chain service is not the same as cashing out or completing an exchange of the entire stolen amount. Some operations received refunds, and some downstream recipients remained unresolved within the snapshot. A complete account of the assets' subsequent disposition is therefore still outstanding.

The response from teams and exchanges

K3's confirmed response is the contract pause. Liquity identified the boundary of the affected product and said it was supporting the investigation. Neither statement establishes that reserves have been restored or that depositors have received compensation.

The reviewed sources do not provide a confirmed inventory of exchange-frozen assets, an agreed recovery bounty or completed negotiations. The timeline will be updated when primary evidence establishes those developments; an absent announcement is not replaced by an assumed outcome.

What it means for holders

A vault vulnerability and an underlying protocol failure are different events. Liquity's statement about V2 does not guarantee recovery for sBOLD holders. An individual holder's exposure depends on their position; a total outflow estimate is not sufficient to calculate a personal compensation amount.

This timeline does not have a separately verified sBOLD price series. Changes in ETH or BOLD cannot automatically be attributed to the exploit. Losses in derivative positions are likewise excluded without a separate calculation. The main outstanding questions are the final accounting, the deployed code version, recoveries and the terms of any future operation.

See the initial news report and the CoinLab daily brief for wider market context.

This is not investment advice.

This story is developing. We follow new evidence and update this timeline. Last updated November 18, 2026, 04:19 PM ET.

Morning brief and news on TelegramEvery morning at 9:00 AM ET, before the US open: price, 24h scenario, squeeze risk. Key news around the clock.
Coins
Category
Tags
#K3 Capital#sBOLD#exploit#DeFi
Ryan Mitchell
On-chain and mining

Breaks down blockchain and mining data: hashrate, difficulty, holder and whale behavior.

Comments

Read next