Key Highlights:
- Blockchain security firm Blockaid identified concurrent security exploits impacting the K3-developed sBOLD vault and tokenized real estate lending platform Reental.
- Attackers drained the sBOLD vault using wrapped staked ether (wstETH) flash loans and forced self-liquidations to mint cheap vault shares and redeem underlying depositor capital.
- Reental suffered a stablecoin loss estimated at $454,000 after an administrator key upgraded USDT and USDC proxy contracts to allow unauthorized token withdrawals.
Security Exploits Hit sBOLD Stability Vault and Reental Lending Platform
Decentralized finance protocols faced dual security breaches after security monitoring firm Blockaid reported ongoing exploits targeting the sBOLD yield vault and real estate tokenization platform Reental. The separate incidents involved distinct attack vectors, ranging from complex economic manipulation through flash loans to the direct tampering of administrative smart contract proxies.
Flash-Loan and Self-Liquidation Mechanism Depletes sBOLD Vault
According to Liquity’s documentation, sBOLD operates as an automated compounding vault designed to reinvest rewards from $BOLD stablecoins deposited into Liquity V2’s Stability Pools. These stability pools absorb undercollateralized debt from borrowing positions in exchange for collateral and collect interest paid by platform borrowers. Although the vault interfaces directly with Liquity V2 infrastructure, the smart contracts were engineered and maintained by third-party developer K3, rather than Liquity’s core development team. Depositors receive sBOLD shares as a representation of their proportional balance within the vault.
Blockaid reported that the attacker executed the exploit by acquiring a flash loan denominated in wrapped staked ether (wstETH) to manipulate collateral parameters. The exploiter deliberately triggered the liquidation of their own Liquity borrowing position, which allowed them to artificially acquire sBOLD shares at a significantly depressed valuation. With newly minted, undervalued shares in hand, the attacker completed collateral swaps and redeemed $BOLD stablecoins belonging to other vault depositors, siphoning the vault’s backing assets.
The self-liquidation vector had previously been analyzed prior to the attack. A May 19, 2025, ChainSecurity audit of the codebase examined self-liquidation risks and noted that the ability to extract funds via that vector “has been mitigated” in Version 3 of the evaluated smart contracts. However, the historical report does not confirm whether the recent incident exploited the same technical vulnerability or an unaddressed edge case. Following the incident, K3 instituted an emergency pause on the sBOLD contract, though its initial communications did not detail the precise technical root cause or present reimbursement terms for impacted depositors.
Unauthorized Proxy Upgrade Clears Stablecoins from Reental
In a separate alert, Blockaid uncovered an exploit affecting Reental, a decentralized lending protocol where users pledge tokenized real estate assets as collateral to borrow stablecoins under its RNT Lend program. Unlike the market manipulation seen in the sBOLD event, Reental’s breach stemmed from smart contract administrative access.
Blockaid revealed that an administrator address executed a contract upgrade on Reental’s underlying $USDT and USDC deposit-token proxies. The updated code modified access controls to allow arbitrary addresses to withdraw underlying tokens, paving the way for the remaining stablecoin reserves to be drained. Blockaid’s notice did not establish whether the administrator account was deliberately compromised, abused by an insider, or altered for another purpose.
Public ledger data confirms substantial outflows matching the attack profile. A transaction recorded on PolygonScan at 6:41 a.m. ET on Nov. 18 shows the unauthorized transfer of roughly 294,040 USDT0 from one of the affected contracts flagged by Blockaid to an external address. While this documented transfer accounts for a significant portion of the movement, total platform damages are estimated near $454,000.
Why This Matters
The simultaneous incidents underscore persistent structural vulnerabilities within decentralized finance architectures, specifically highlighting third-party integration risks and centralized smart contract governance. While Liquity V2’s core protocol contracts remained structurally intact, the sBOLD incident illustrates how secondary wrapper vaults and yield-aggregating layers can introduce unexpected economic attack surfaces through flash loans and liquidation mechanics.
Concurrently, the Reental exploit highlights the inherent trade-offs associated with upgradable proxy contracts. When governance controls or administrator private keys are compromised, proxy upgrade capabilities allow threat actors to bypass standard protocol logic entirely. With Blockaid characterizing both exploits as active at the time of discovery and K3 yet to announce a reopening date or restitution framework, affected depositors remain faced with unresolved recovery paths.
Frequently Asked Questions
Did the exploit on sBOLD compromise Liquity V2’s core protocol?
No. Liquity’s documentation notes that the sBOLD vault was independently developed and managed by K3, not Liquity’s core team. The vulnerability existed in the interaction and valuation logic of K3’s sBOLD vault contracts rather than Liquity V2’s base Stability Pool code.
How were funds extracted from Reental’s lending contracts?
An administrator address pushed an unauthorized upgrade to Reental’s $USDT and USDC proxy contracts on the Polygon network. The new code contained logic permitting arbitrary callers to withdraw underlying collateral, allowing the attacker to sweep out stablecoins, including a verified on-chain transfer of approximately 294,040 USDT0.
What steps have been taken to secure the protocols?
K3 deployed an emergency pause on the sBOLD vault to halt ongoing draining of the contracts, though it has not yet provided a timeline for resumption or a compensation strategy. Regarding Reental, security firms flagged the incidents as ongoing while the origin of the administrative key compromise remains under evaluation.




