Incident facts
| Affected party | K3 Capital sBOLD |
|---|---|
| Event date | November 18, 2026 |
| Network | Ethereum |
| Status reported by source | Attack contained |
| Estimated loss | $3,430,000 |
| Frozen | No confirmed data |
| Returned | No confirmed data |
What happened
K3 Capital’s sBOLD vault was drained on 18 November and paused at 13:05 UTC. In a 19 November postmortem reported by The Crypto Times, the project put the loss at approximately 3.43 million BOLD across 99 transactions.
The report attributes the exploit to a swap that left collateral unspent and a router approval active. This allowed repeated overvalued redemptions and collateral removal. It says Liquity V2 and 1inch themselves were not exploited, correcting the early self-liquidation explanation.
K3 offered a 15% bounty on returned funds and plans to distribute recoveries to affected depositors. The announcement describes a recovery process, not completed reimbursement or a guaranteed payout.
Sources
- The Crypto Times — K3 postmortem and recovery terms — Report · www.cryptotimes.io · November 19, 2026
- SigIntZero — swap and approval analysis — Analysis · sigintzero.com · November 19, 2026
- Bitquery — transaction reconstruction — Analysis · bitquery.io · November 18, 2026
Information is attributed to the linked sources and has not been independently verified by Match Systems. Loss estimates and incident status may change as new evidence becomes available.
Latest incidents
- ExploitLookonchain tracks another 137,602 ETH from Binance-linked hack wallets
- Under investigationXMR1 faces suspected security incident after deployer transfers
- ExploitPaytaca reports backend attacks creating fake payment requests
- Supply chain attackCALC reports treasury losses as Keplr opens a recovery checker
- ExploitLUKSO shuts down email recovery after about 300 profiles are hit
- Key compromisePeapods withdraws L2 liquidity after a suspected key compromise