A post by @Phalcon_xyz on X.
.@k3_capital’s sBOLD vault was reportedly exploited, with losses exceeding $3.42M. The team has paused the affected contracts. The root cause was insufficient swap-input validation combined with uncleared router allowances, allowing the…
@Phalcon_xyz on X
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
K3 Capital’s sBOLD vault was exploited for more than $3.42 million after an attacker manipulated the vault’s share price, prompting the team to pause the affected contracts. BlockSec Phalcon attributed the root cause to insufficient swap-input validation combined with uncleared router allowances, which let the attacker donate 4 WETH, supply BOLD from another source to satisfy the minimum-output check, and inflate totalAssets without minting new sBOLD shares. The attacker then redeemed at the elevated share value and used a second swap nominally for 1 wei of wstETH to recover the donated WETH via the router’s leftover allowance, repeating the deposit–donate–swap–redeem–recover cycle to extract roughly $3,000 per round at other depositors’ expense. The incident matters because it exposes how share-price accounting and allowance hygiene in vault swap logic can be drained even when balance checks appear to pass. What to watch next is whether K3 Capital restores the paused contracts with tightened input binding and allowance clearing, and how sBOLD depositors are made whole.
Muhabbit's AI wrote this summary of @Phalcon_xyz's post in its own words. It can get details wrong, so read the post on X.
Named in this story
K3 Capital, sBOLD, BOLD, BlockSec Phalcon, WETH, wstETH