Hacks & Security · Explained
K3 Capital and Reental lose nearly $3.9M in separate DeFi exploits
Blockaid flagged ongoing attacks against K3 Capital's sBOLD vault on Ethereum and Reental's Polygon contracts, with losses estimated at about $3.88 million.
Key takeaways
- Different mechanisms. K3 Capital's loss involved sBOLD share valuations and Liquity V2 liquidations, while Reental's loss followed an administrative upgrade to stablecoin proxy contracts.
- Audit history. A May 2025 ChainSecurity audit said value extraction through self-liquidations had been mitigated; it is unclear whether the Nov. 18 attack used that route.
- Ongoing warnings. Blockaid described both incidents as ongoing when it disclosed them, and K3 Capital paused its contracts while saying it was investigating.
What happened
Blockchain security firm Blockaid flagged two separate DeFi exploits on Nov. 18, saying attackers had drained about $3.43 million from K3 Capital's sBOLD vault on Ethereum and roughly $454,000 from Reental on Polygon. The combined losses were approximately $3.88 million, or nearly $3.9 million, according to Crypto.news. Blockaid described both incidents as ongoing when it issued its alerts.
Unchained reported that Blockaid's K3 Capital alert went out at 12:50 UTC. K3 Capital responded on X about 17 minutes later, saying it was investigating malicious activity involving sBOLD and that contracts had been paused. The operator did not disclose a loss figure or a cause. Unchained also noted that one transaction Blockaid highlighted had been recorded on Ethereum at 12:25 UTC and contained 231 separate token transfers.
Blockaid said the K3 attack began with a flash loan in wstETH, Lido's wrapped staked ether. The attackers then liquidated their own Liquity V2 borrowing position, pushing its debt and collateral into the protocol's stability pools. According to Blockaid, they created sBOLD shares at artificially low valuations, exchanged collateral and redeemed BOLD that belonged to other vault depositors.
In the Reental case, Blockaid reported that an administrator upgraded proxy contracts tied to USDT and USDC deposit tokens, often called aTokens. The upgrade introduced a contract that allowed any party to withdraw the tokens backing those deposits, and the remaining stablecoin balances were then moved out. About $454,000 had been drained across two transactions when Blockaid disclosed the incident. The firm identified an exploiter address and two affected smart contracts.
Why it matters
The two cases point to different security weaknesses. K3 Capital's sBOLD is a third-party yield vault built on Liquity V2, and its adjustable components, including a price oracle and a token-swap adapter, set it apart from Liquity V2's immutable core contracts. Reental's loss followed an administrative upgrade, putting attention on privileged changes to proxy contracts. For depositors, the incidents show how losses can arise from contract design, liquidation mechanics and upgrade authority rather than a single shared vulnerability. They also add to a busy month for DeFi security, with several other losses reported in November.
What the data shows
Blockaid's initial K3 Capital figure was about $3.43 million across roughly 34 Ethereum transactions as of 12:50 UTC, and the firm said the attack was ongoing, so the tally could change. The Reental loss was about $454,000 across two transactions at disclosure. Combined, the two incidents represented about $3.88 million. The reports also placed them alongside other November incidents: about $3.76 million at pre-attack valuations from the Kava Lend exploit, a reported $6.45 million loss from a Gnosis Safe wallet on Nov. 16, and about $38,200 taken from Curve Finance through 138 unauthorized trades on Nov. 10.
Background
sBOLD is an ERC-4626 vault. Users deposit BOLD, Liquity V2's dollar-pegged stablecoin, and the vault places the funds in Liquity's stability pools, which repay liquidated loans and receive collateral in return. Liquity's blog describes sBOLD as a K3 Capital project, not part of Liquity's core protocol. ChainSecurity completed an audit of sBOLD on May 19, 2025. Its summary said the possibility of value extraction through self-liquidations had been mitigated, and the audit listed two critical, three high-severity and eight medium-severity findings, all marked corrected. A separate May 2025 Dedaub assessment examined the vault's reliance on BOLD market liquidity and its valuation. Whether the Nov. 18 attack used the previously identified self-liquidation route remains unknown.
What is still unclear
K3 Capital has not said what caused the sBOLD exploit, whether it matched the risk described in the 2025 audit, or what depositors can expect. No final loss figure has been published, and Blockaid's number reflected the situation at the time of its alert. Crypto.news said it had contacted K3 Capital but received no response by press time. The reports did not provide a response from Reental.
What to watch
K3 Capital's investigation and the paused sBOLD contracts are the immediate items to follow, along with any revised loss figures. The coming disclosures may clarify whether the audited self-liquidation scenario was involved and how depositors will be treated. On the broader front, Curve's governance proposal to replace its vulnerable fee-conversion contract remained open until Nov. 20, according to Crypto.news.
Questions readers ask
What happened to K3 Capital's sBOLD vault?
Blockaid said attackers drained about $3.43 million across roughly 34 Ethereum transactions. K3 Capital said it was investigating and had paused the contracts, but did not disclose a cause or final loss figure.
How did Reental lose funds?
Blockaid reported that an administrator upgraded proxy contracts for USDT and USDC deposit tokens, introducing a contract that allowed the underlying tokens to be withdrawn. About $454,000 was drained across two transactions on Polygon at the time of disclosure.
Are the K3 Capital and Reental attacks related?
The reports describe them as separate exploits using different methods, one involving sBOLD share valuations and Liquity V2 liquidations, and the other involving an administrative upgrade to Reental's stablecoin contracts.