0x58fe59f658fe…58fe59f3

ConfirmedSecurity570 vB106 sat/vB3 min decode

Blockaid Flags $3.43 Million Exploit on K3 Capital's sBOLD Vault

Blockaid flagged an ongoing $3.43M exploit of K3 Capital's sBOLD vault on Ethereum. The attacker used wstETH flash loans and a self-liquidated Liquity V2 trove to mint shares cheaply.

Blockaid flags ongoing $3.43 million exploit on K3 Capital’s sBOLD vault
WitnessBlockaid flags ongoing $3.43 million exploit on K3 Capital’s sBOLD vaultFelix-Mittermeier / pixabay

Outputs

  1. Blockaid flagged an ongoing exploit of K3 Capital's sBOLD vault on November 18, 2026, with ~$3.43 million drained.

  2. The attacker used wstETH flash loans and a self-liquidated Liquity V2 trove across roughly 34 transactions to mint sBOLD shares at a discount.

  3. sBOLD is an audited ERC-4626 vault; ChainSecurity reviewed it in May 2025 before its ~June 2025 launch.

  4. Reental, a tokenized real estate platform on Polygon, lost ~$454,000 in a separate exploit the same day, bringing total reported losses to ~$3.9 million.

Blockchain security firm Blockaid flagged an active exploit on November 18, 2026 that drained approximately $3.43 million from sBOLD, a yield vault built by K3 Capital on Ethereum. The attack was still in progress when the alert went out, leaving depositors watching losses accrue in real time rather than reading about them after the fact.

According to research findings tied to Blockaid's report, the attacker executed roughly 34 transactions using two tools: flash loans of wstETH — wrapped staked Ether, the liquid token representing ETH staked through Lido — and a deliberately self-liquidated borrowing position, or trove, on Liquity V2.

How did the attack work?

On Liquity V2, a trove is a borrowing position where users lock collateral and mint BOLD, the protocol's stablecoin. sBOLD parks its users' BOLD deposits into Liquity V2's stability pools, earning yield from borrower interest and liquidation premiums.

The attacker liquidated their own trove into those same stability pools. By pushing the liquidation through, they minted sBOLD shares at a discount, then swapped collateral and redeemed deposits belonging to other users. A flash loan, for context, is a short-term DeFi loan borrowed and repaid within a single transaction — the attacker's leverage of choice.

The mechanics matter because liquidation premiums sit at the heart of sBOLD's accounting. The vault earns when troves get liquidated, so its share pricing is directly tied to liquidation events. Manipulating one of those events was the way in.

Why was sBOLD a target?

sBOLD is an ERC-4626 vault — the standard format for tokenized vaults on Ethereum, designed so other protocols can integrate it without custom wiring. K3 Capital launched it around June 2025, pitching it as a delta-neutral product that improves capital efficiency through composability with other DeFi protocols.

That composability cuts both ways. Any protocol that accepts sBOLD as collateral or builds strategies around it may now need to assess its own exposure.

Wasn't the vault audited?

Yes. ChainSecurity audited sBOLD in May 2025, shortly before launch. The research findings describe that audit as identifying weaknesses and highlighting improvements — but it could not eliminate every vulnerability in the system. An audit is a snapshot, not a guarantee, and this exploit proves the gap between the two.

What does this change for depositors and builders?

For sBOLD depositors, the immediate concern is that losses are not yet final. Because the attack was described as ongoing when Blockaid raised the alarm, the $3.43 million figure could still move, and users holding sBOLD have reason to monitor updates from K3 Capital and security firms closely.

For builders, the exploit is a case study in how vault architectures tied to liquidation mechanics can be gamed from the inside. Flash-loan-assisted self-liquidation is not a new technique, but sBOLD shows it remains effective against audited, standard-contract deployments.

A second exploit the same day

sBOLD was not the only casualty on November 18. Reental, a tokenized real estate platform running on Polygon, reported a separate exploit costing approximately $454,000. The two incidents are unrelated, according to the research. Combined, they push reported losses for the day to roughly $3.9 million.

With the sBOLD attack still unfolding and K3 Capital yet to publish a full post-mortem, the coming days will determine the final loss figure, any compensation plan for depositors, and whether integrated protocols move to sever exposure to the vault.

via Crypto Briefing (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,456 articles