K3 Capital and Reental Crypto Hack: How Two DeFi Exploits Drained $4.38M
A flash loan manipulated sBOLD vault pricing, while proxy upgrades exposed Reental’s lending markets. Learn how both exploits unfolded and which contract risks to check before depositing.
On November 18, 2026, two separate DeFi incidents involving K3 Capital and Reental led to approximately $4.38 million in cryptocurrency outflows. The crypto hack at K3 Capital exploited how an Ethereum vault priced its shares; Reental’s Polygon lending app was drained after an administrator changed its contract logic.
Neither incident required stealing ordinary depositors’ private keys. Once assets enter a DeFi protocol, their safety also depends on how its contracts value deposits and who can change the rules governing withdrawals.
What Happened in the K3 Capital and Reental Crypto Hack?
Bitquery’s on-chain investigation traced $3.42 million leaving K3 Capital’s sBOLD vault in eight minutes, across 97 transactions from six addresses. Its separate Reental investigation found $954,703 in stablecoin outflows, more than twice the initial estimate of about $454,000.
K3 Capital exposed an accounting flaw; Reental exposed dangerous upgrade authority.
Attack Timeline: November 18, 2026
- Reental Admin Upgrade
An administrator-controlled address deploys replacement implementations and changes the logic of two stablecoin markets.
- MEV Bots Intervene
Two bots extract $454,825 through the new withdrawal path before the keyholder completes the intended transfers.
- Further Withdrawals
The keyholder withdraws another $499,877 from 1,149 user wallets and four Safe contracts.
- sBOLD Drained
Six addresses complete 97 transactions, extracting approximately $3.42 million from K3 Capital’s vault.
- Reental Response
Reental removes the implicated key, pauses its lending pool and replaces code for 91 affected markets.
Reental also recovered property tokens valued internally at $49.34 million within approximately two hours. This valuation excludes stablecoin losses.
How the Flash Loan Attack Exploited sBOLD Share Pricing
K3 Capital built sBOLD on Liquity V2. Users deposited BOLD stablecoins and received shares in a vault that deployed funds across Liquity Stability Pools. The share price was supposed to represent each depositor’s portion of the vault’s assets.
The flaw arose because WETH collateral held by the vault was not fully counted in its share valuation. Converting that WETH into BOLD increased the value recognized by the accounting formula, even though the economic value had already belonged to the vault.
How Flash Loans Work in This Exploit
A flash loan provides capital that must be repaid within the same blockchain transaction. If repayment fails, the entire transaction reverts. This made it possible to execute a large sequence of deposits and redemptions without maintaining the equivalent capital beforehand.
- Borrow capital. In one reconstructed transaction, the attacker borrowed 10,000 wstETH through Morpho, posted collateral in Liquity V2 and created roughly 9 million BOLD.
- Acquire discounted shares. The attacker deposited BOLD into sBOLD while WETH remained incompletely reflected in the vault’s share price.
- Change recognized value. The vault’s swap() function converted WETH into BOLD, causing the share valuation to rise.
- Redeem and repeat. The attacker redeemed the appreciated shares, extracting approximately 10,600 additional BOLD per cycle, repeated the process eight times and then repaid the borrowed capital.
Bitquery’s transaction reconstruction estimates that particular transaction extracted about $23,000. The same technique was repeated by several addresses. A copycat MEV bot alone extracted around $1.91 million, while block builders received approximately $1.78 million in priority payments.
Why an Earlier Smart Contract Audit Did Not Prevent the Exploit
A 2025 audit by ChainSecurity had already documented a related valuation vulnerability as finding CS-SBOLD-008. It described how excluded collateral could permit discounted share issuance followed by redemption at a higher value. The finding was marked fixed in the third reviewed code version.
Early alerts claimed attackers liquidated their own borrowing positions to bring collateral into the vault. Bitquery found no liquidation during the drain: WETH was supplied directly. It remains unclear which exact fixes were deployed in the attacked implementation and why the accounting flaw persisted.
This resembles the Arcus accounting exploit, where incorrect internal balance accounting allowed unauthorized withdrawals. In sBOLD, the error affected the value assigned to the entire vault’s shares rather than a single user balance.
How a Proxy Upgrade Enabled the Reental DeFi Exploit
Reental’s RNT Lend used upgradeable contracts on Polygon, based on an Aave V3-style lending architecture. A proxy keeps the address users interact with unchanged, while forwarding calls to a separate implementation that contains the actual logic.
Administrators can replace the implementation without moving deposits, potentially changing withdrawal rules after users deposit.
What Changed Inside Reental’s Contracts?
According to Bitquery’s analysis, an administrator-controlled address replaced implementations behind the USDT0 and USDC markets. The initial new logic permitted arbitrary callers to transfer underlying assets to chosen recipients without normal authorization checks.
Two MEV bots noticed the exposed withdrawal path and extracted $454,825 before the keyholder’s own calls completed. The keyholder later introduced more restricted logic and withdrew another $499,877 from 1,149 user wallets and four Safe contracts, routing the proceeds through bridges.
Blockchain records confirm administrative access, not whether the key was stolen or misused. Reental removed the key, paused the pool and replaced affected implementations.
DeFi Security Checklist: What to Verify Before Depositing
The question “is DeFi safe?” needs a protocol-specific answer. A smart contract audit checklist should address not only the code reviewed at one point in time but the permissions that can alter it after a user deposits.
- Audited version. Confirm which deployed contracts were reviewed, which findings remain open and whether the deployed implementation matches the audited revision.
- Upgrade authority. Identify the ProxyAdmin or equivalent role and check whether it can replace asset-transfer or withdrawal logic.
- Key governance. Determine whether one signer can approve a change or a multisignature threshold is required. Multisig reduces single-key dependence but does not remove all governance risk.
- Timelock smart contract. Look for a mandatory delay before upgrades take effect, and check whether emergency roles can bypass it.
- Withdrawal protections. Review rate limits, emergency pause rights and liquidity available for redemptions. A pause may restrict attackers and legitimate users alike.
- Vault mathematics. Inspect whether collateral, rewards, conversions and liabilities are all correctly reflected in share valuation.
Reental’s $10.01 million in lender deposits was backed by only about $454,825 of immediately available stablecoin liquidity at the time. The broader distinction between holding keys and entrusting assets to another system is explained in our custodial versus non-custodial wallets guide.
FAQ: The K3 Capital and Reental Crypto Hack
How Much Did K3 Capital and Reental Lose?
Bitquery identified approximately $3.42 million leaving sBOLD and $954,703 in Reental stablecoin outflows, totaling around $4.38 million as of November 19, 2026.
Was Liquity V2 Itself Hacked?
The reported accounting flaw affected K3 Capital’s sBOLD vault, which used Liquity V2 Stability Pools. It was not evidence that all Liquity V2 markets had been compromised.
Was Reental’s Admin Key Stolen?
The transactions used valid administrative permissions. Public blockchain records do not establish whether the key was stolen or misused by an authorized holder.
How Do Crypto Flash Loans Work?
A flash loan is borrowed and repaid in one atomic transaction. If the repayment condition fails, the entire transaction reverts.
Do Flash Loans Still Work?
Yes. The November 18 sBOLD exploit shows their continued use. Flash loans are not inherently malicious, but they can amplify vulnerabilities in other contracts.
The Bottom Line
K3 Capital lost funds through an accounting error in share pricing. Reental’s losses followed a replacement of contract logic under existing administrator authority. Before depositing a significant amount, verify the current implementation, unresolved findings, upgrade permissions, timelocks and redemption controls. A single key capable of immediately changing withdrawal logic deserves particular scrutiny.

Control your keys. Know what controls your deposits.
Use the code below for 20% off.