55ba633e-8
K3 Capital Halts Ethereum sBOLD Contracts After $3.43M Exploit
K3 Capital paused sBOLD contracts 18 minutes after Blockaid flagged a $3.43M flash-loan exploit targeting Liquity V2 Stability Pool rewards on Ethereum.

Outputs
Blockaid flagged ~$3.43 million moved across 34 transactions at 7:50 a.m. ET on Nov. 18
K3 Capital paused sBOLD contracts 18 minutes after the alert, at 8:08 a.m. ET
Attack used a wstETH flash loan, self-liquidation into Liquity V2 Stability Pools, discounted sBOLD minting and BOLD redemption
K3 provided no loss estimate and no confirmation of recovery or frozen funds
sBOLD vault compounds rewards from Liquity V2 Stability Pools holding BOLD deposits
K3 Capital paused the contracts behind its Ethereum sBOLD vault on Nov. 18 after blockchain security firm Blockaid flagged an ongoing exploit that had already moved approximately $3.43 million across 34 transactions.
Blockaid issued its alert at 7:50 a.m. ET (12:50 p.m. UTC), counting roughly 34 transactions at that point. The figure describes observed activity, not a confirmed final loss. Eighteen minutes later, at 8:08 a.m. ET (1:08 p.m. UTC), K3 Capital confirmed it was investigating malicious activity involving sBOLD and had paused the affected contracts. The company offered no loss estimate and gave no indication that funds had been recovered or frozen.
The 18-minute gap between alert and pause is short by incident-response standards, but the exploit's mechanics suggest the damage may have been done before detection.
How the attack worked
Blockaid reconstructed the exploit as a multi-step sequence built around a flash loan in wrapped staked Ether (wstETH):
- A wstETH flash loan funded the initial position.
- The attacker executed a self-liquidation into Liquity V2 Stability Pools.
- Discounted sBOLD was minted.
- Collateral was swapped.
- Other depositors' BOLD was redeemed.
The target, sBOLD, is K3 Capital's vault token that compounds rewards from Liquity V2 Stability Pools, where BOLD deposits are held. The attack path indicates the vulnerability sat in how sBOLD interacts with those pools, specifically in the minting and redemption logic that the exploit chain manipulated in a single atomic transaction set.
What does this change for sBOLD depositors?
For practitioners, the practical question is exposure and recoverability. The $3.43 million figure represents value moved through roughly 34 transactions as of the initial alert; the final number could be higher. K3 has paused the contracts, which stops further exploitation but does not, by itself, freeze assets already extracted. The company has not stated whether the redemption of other depositors' BOLD left the vault undercollateralized, and no recovery or freeze has been announced.
Depositors in Liquity V2 Stability Pools through other protocols are not directly implicated, but integrators that wrap or compound Stability Pool positions now have a concrete case study in how minting discounts and redemption paths can be chained into an extraction attack.
The response window
K3 Capital has not published a post-mortem, a loss figure, or a remediation plan. The investigation is ongoing, and the paused contracts mean sBOLD redemptions are effectively halted until the firm restores them. Expect the next material disclosure, whether a confirmed loss amount or a contract fix, to determine whether this incident remains a contained $3.43 million event or grows into a larger solvency question for the vault.
via tokenpost.com (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,574 articles