Blockaid: attackers steal ~$3.88M from K3 Capital and Reental in two separate DeFi incidents Blockchain security firm Blockaid flagged two active exploits on Nov. 18 that together siphoned roughly $3.88 million from smart contracts on Ethereum and Polygon — hitting K3 Capital’s sBOLD vault and Reental’s stablecoin aTokens. Quick summary - Total drained: ≈ $3.88M - K3 Capital (Ethereum, sBOLD vault): ≈ $3.43M across 34 transactions - Reental (Polygon, USDT/USDC aTokens): ≈ $454K across 2 transactions - Alerts first posted by Blockaid on X (formerly Twitter) on Nov. 18; attackers’ wallets and helper addresses were identified. What happened at K3 Capital - Target: sBOLD, a third‑party yield vault run by K3 Capital that auto‑reinvests rewards from Liquity V2 stability pools. sBOLD shares represent proportional stakes in deposited BOLD; returns come from borrower interest and liquidation proceeds. - Attack technique: flash loans involving wrapped staked ETH (wstETH) to manipulate Liquity V2 liquidations. According to Blockaid, the attacker self‑liquidated a trove into Liquity’s stability pools, minted sBOLD shares at artificially low valuations, swapped collateral and redeemed other depositors’ BOLD — essentially acquiring cheap sBOLD and extracting value from the vault. - Impact: ~34 transactions drained about $3.43M from the vault. Blockaid published an example transaction and flagged the Ethereum address and a helper address tied to the drain. - Background: Liquity’s docs note sBOLD is operated by K3 Capital, not Liquity’s core team. K3 Capital had not responded to requests for comment at press time. Audits and whether this was preventable - May 19, 2025 ChainSecurity audit flagged a high‑severity accounting issue in an earlier sBOLD version: collateral could be mis‑accounted for after liquidations, potentially undervaluing vault shares and enabling value extraction via self‑liquidations. ChainSecurity marked that finding as corrected after changes were applied. - A May 2025 Dedaub review also highlighted risks around BOLD liquidity and correct valuation. - It remains unclear whether the Nov. 18 exploit relied on the previously identified accounting bug or a separate flaw. What happened at Reental - Target: Reental’s proxy aTokens on Polygon representing USDT and USDC deposits for the platform’s tokenized real estate products. - Attack technique: an administrator upgrade replaced the proxy implementations with a contract that allowed anyone to drain the underlying stablecoins. The attacker then swept the remaining balances. - Impact: ~ $454K drained in two transactions. Blockaid identified an address and two affected contracts. - About Reental: the platform tokenizes property‑related loans and shares tied to investments in Spain and the U.S. Wider context: a spate of recent DeFi incidents - Earlier this week Kava Lend lost ≈ $3.76M after an attacker exploited an accounting weakness in a dormant BUSD lending market. - A Gnosis Safe wallet reportedly lost ≈ $6.45M on Nov. 16 in a suspected exploit tied to preconfigured transaction permissions. - Curve Finance disclosed ~ $38.2K stolen from administrative revenue across 138 unauthorized trades on Nov. 10, exploiting a fee‑conversion contract. Curve said user deposits and lending markets were unaffected and a governance proposal to replace the vulnerable contract was open until Nov. 20. What to watch next - Onchain forensic tracking of the attacker addresses and any attempted token swaps or bridged flows. - Responses from K3 Capital and Reental, potential contract freezes or emergency upgrades, and recovery or restitution efforts. - Whether post‑mortem analyses will link these drains to previously identified audit findings or reveal novel vulnerabilities. This remains an active story; Blockaid’s X thread contains transaction examples and addresses flagged during the alerts. Read more AI-generated news on: https://app.chaingpt.org/news