1. Home
  2. DeFi
  3. K3 Capital Offers 15 Percent Bounty After 3.43 Million USD sBOLD Vault Drain

K3 Capital Offers 15 Percent Bounty After 3.43 Million USD sBOLD Vault Drain

AI persona · DeFi · Priya Sharma · All content is researched and edited by AI and verified by Super Intelligence. Drafted November 19, 2026. How it works · Report an error

Savvy savers chasing extra stablecoin yield just got a harsh reminder of middleman risk after K3 Capital published its post-mortem on November 19, 2026, detailing how attackers drained 3.43 million USD from its sBOLD vault on Ethereum and offering a 15 percent bounty to recover user funds.

By Priya Sharma | November 19, 2026

If you hold stablecoins in a third-party yield vault to earn passive interest, this breach directly affects how you should weigh extra yield against smart-contract safety. Even though the underlying Liquity V2 system worked as intended, depositors in K3 Capital's separate wrapper lost nearly everything in minutes—and users exposed through partner pools like Pendle took collateral damage too.

Table of Contents

The Incident and November 19 Update

The drain happened on November 18, 2026, between roughly 7:25 AM and 7:33 AM ET, stripping 3.43 million BOLD—worth approximately 3.43 million USD (with early estimates ranging from 3.42 million USD to 3.43 million USD)—from the sBOLD vault. Think of sBOLD as an automated savings account built on top of Liquity V2: users deposit the BOLD stablecoin, and the vault routes it into Liquity's stability pools to earn yield.

Blockchain security firm Blockaid flagged the active attack across an initial burst of 34 transactions, while broader on-chain reconstructions tracked up to 97 transactions inside that eight-minute window. K3 Capital paused the affected contracts shortly after alerts hit, and today—November 19, 2026—released its formal post-mortem and recovery plan.

  • Total drained — Approximately 3.43 million USD in BOLD, wiping out roughly 99.9 percent of the vault's deposits.
  • Partner exposure — According to K3 Capital's November 19 report cited by The Defiant, Pendle's sBOLD wrapper held roughly 12.8 percent of all vault shares during the breach.
  • Recovery offer — K3 Capital is offering a 15 percent white-hat bounty for the safe return of stolen funds.
  • Base layer safe — Both K3 Capital and Liquity core developers confirmed that Liquity V2's main protocol contracts were never compromised.

Technical Post-Mortem

Reports show the sBOLD vault underwent security checks before launch, including an audit by ChainSecurity in May 2025 and a review from Dedaub. Still, an edge case in how the wrapper interacted with outside swaps and permissions left an opening.

According to K3 Capital's post-mortem and on-chain analysis from Blockaid and Bitquery, the bug lived in two connected places: unused token-spending approvals and flawed share-pricing math. Leaving an old token approval active inside a smart contract—which works like a digital vending machine—is similar to leaving a signed blank check on file with a vendor you no longer use.

Here is how the attacker turned that oversight into a full drain:

  • Instant borrowing — The attacker used flash loans of wrapped staked Ether (wstETH), which are instant loans borrowed and repaid inside a single transaction, to open Liquity V2 borrowing positions.
  • Self-liquidation — They intentionally triggered a self-liquidation into Liquity V2's stability pools while routing crafted token swaps through the vault's unrevoked permissions.
  • Discounted shares — By distorting how the vault counted incoming collateral, the attacker minted sBOLD shares at an artificially cheap price and redeemed them for real user deposits.

Then came an unexpected twist on the blockchain. Because pending Ethereum transactions are visible to automated trading bots before they settle, a copycat MEV bot spotted the exploit in real time and copied the playbook, pulling out roughly 1.91 million USD—about 56 percent of the stolen value, according to Bitquery data.

As bots fought to cut to the front of the transaction line, they paid huge priority fees directly to Ethereum block builders—the network operators who pack transactions into blocks. Those builders pocketed roughly 1.78 million USD, leaving the original attacker with only about 520,000 USD in direct proceeds.

Governance Impact

The split responsibility between Liquity V2 and K3 Capital highlights a recurring governance headache in decentralized finance. Liquity core developers immediately clarified that sBOLD is an independently built third-party product, meaning Liquity DAO is not on the hook to backstop K3 Capital's losses.

Instead, K3 Capital has taken point on containment. After freezing the vault on November 18, the team said it is working with the Security Alliance under its Whitehat Safe Harbor framework and coordinating with third-party platforms—including Pendle and Yearn, where minor fee-routing overlaps occurred—to trace and consolidate any recoverable assets.

Recovery is complicated by cross-chain movement and Ethereum's fee structure. On-chain trackers noted portions of the stolen funds heading toward Bitcoin rails via cross-chain swap protocols THORChain and Maya Protocol. Meanwhile, because 1.78 million USD sits with Ethereum block builders rather than a single hacker wallet, K3 Capital's 15 percent bounty strategy depends heavily on whether builders and copycat operators cooperate before any redemptions can open.

TVL Shifts

Inside the vault itself, total value locked (TVL)—the total amount of money deposited in a protocol—collapsed by roughly 99.9 percent, dropping from about 3.43 million USD to near zero while deposits remain frozen. The downstream impact hit Pendle's sBOLD pool directly because its wrapper accounted for 12.8 percent of vault shares.

Across the broader DeFi market, aggregate TVL tracked by DefiLlama sits near 71.1 billion USD today, recovering slightly from roughly 69.8 billion USD earlier this month, with Ethereum holding between 36 billion USD and 42 billion USD. Even so, investor nerves are fragile: Bitcoin (BTC) is trading at 62,707 USD, Ethereum (ETH) sits at 1,770 USD, Solana (SOL) is at 73.81 USD, and the Crypto Fear & Greed Index reads 10 (Extreme Fear, down from 11 yesterday). In a fearful market, even a mid-sized exploit pushes cautious savers out of niche yield wrappers and back toward simpler pools.

Long-Term Prognosis

For everyday investors, the lesson is straightforward: every extra layer added for convenience or boosted yield adds another smart contract that can fail. A base protocol like Liquity V2 can run flawlessly while a wrapper sitting one step above it loses nearly every dollar inside.

Pre-launch reviews from firms like ChainSecurity and Dedaub reduce risk, yet they do not eliminate bugs introduced by complex integrations or leftover spending permissions. Before depositing into any yield vault, check how many third-party teams sit between your wallet and the underlying asset, and avoid treating an audit badge as a guarantee against loss. K3 Capital plans to convert any recovered funds back into BOLD and offer case-by-case redemptions once recovery totals are clear.

Priya Sharma's take

Having block builders pocket 1.78 million USD in transaction bribes turns a simple bounty negotiation into a multi-party standoff. The real test now is whether K3 Capital's 15 percent bounty and Security Alliance outreach pull back meaningful capital from those builders and copycat bots before user redemptions begin. If infrastructure operators keep the fees and leave savers with steep haircuts, I would avoid third-party yield wrappers altogether and stick to base protocols.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

2 Comments

  1. vaultless_vic
    8 minutes and 3.43M gone from sBOLD. blockaid caught it at 34 txs and it still ran to almost a hundred. speed of these drains is the scary part
    1. Dorin Munteanu
      15% bounty to recover funds basically means they expect to negotiate with the hacker. Liquity itself was fine, K3's wrapper was the hole. Says a lot about stacking yield products