CVE Index中文
L4 · Septic Tank BlewDeFi · Ethereum · sBOLDk3-sbold-vault

K3 Capital pauses sBOLD after a multimillion-dollar vault drain

K3 Capital paused its sBOLD vault after malicious activity. Blockaid estimated about $3.43M drained; Bitquery later counted 97 transactions and about $3.42M. Liquity says V2 itself is unaffected. The attack-path accounts differ.

Disclosed
Nov 18, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
Depositors in K3 Capital’s independent Ethereum sBOLD vault; Liquity V2 is separately scoped
DeFi · Ethereum · sBOLD
In the wild
Yes
K3 confirms malicious activity and a pause; researchers report the vault drain.

What happened

K3 confirms malicious activity and paused contracts. Liquity says the independent sBOLD vault is affected, not Liquity V2. Confirmed exploitation and deposit exposure support L4.

Bitquery estimates about $3.42M across 97 transactions; Blockaid’s preliminary alert estimated about $3.43M. These are attributed estimates, not K3’s final loss total. Blockaid describes self-liquidation; Bitquery found no trove liquidations and instead describes direct WETH transfers exploiting share valuation. Bitquery did not check the deployed code version, so its audit comparison does not prove an old fix was absent. A project postmortem and final recovery accounting remain outstanding.

Crime-scene timeline

  1. Nov 18, 2026

    K3 pauses contracts; Liquity warns against deposits

    The project investigates malicious activity. Liquity distinguishes the independently operated vault from V2.

  2. Nov 18, 16:14 UTC

    Bitquery records its investigation snapshot

    Its analysis counts 97 drain transactions and about $3.42M; these are research estimates, not a final project accounting.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.