Thu. Nov 19th, 2026

Crypto hack roundup: K3, Reental and Binance

ByJohan Shamshad

November 19, 2026 #crypto hack

Three cryptocurrency security developments on November 19, 2026, involve approximately $4.4 million in newly investigated DeFi losses and another $248 million in Ether movements linked to the October Binance hack. K3 Capital’s sBOLD vault was emptied through a share-pricing exploit, with automated trading bots and Ethereum block builders capturing much of the proceeds. A separate investigation nearly doubled the estimated stablecoin losses at Reental’s RNT Lend platform to $955,000, while wallets associated with the Binance attacker redistributed another 137,602 ETH. Today’s crypto hack roundup examines the revised loss figures, competing on-chain transactions and the continuing movement of stolen assets.

K3 Capital loses $3.43 million as MEV bots exploit sBOLD vault

K3 Capital’s sBOLD vault on Ethereum lost approximately $3.43 million on November 18 after attackers exploited a weakness in the way the vault calculated the value of its shares. Blockchain security company Blockaid identified the attack at approximately 12:50 UTC, while K3 Capital subsequently confirmed malicious activity and announced that the affected contracts had been paused.

A subsequent investigation by blockchain analytics firm Bitquery identified a larger group of transactions than initially reported. According to its findings, six wallets executed 97 draining transactions between 12:25:23 and 12:33:35 UTC, removing approximately $3.42 million from the vault in just over eight minutes.

Eight minutes, that was all it took.

Bitquery found that a copycat maximal extractable value (MEV) bot captured approximately $1.91 million, representing 56% of the total value drained. The bot executed 57 of the 97 transactions, repeatedly exploiting the same mechanism while competing against the wallets that initiated the attack.

Most of the bot’s proceeds did not remain with its operator. Bitquery traced approximately $1.78 million in payments to Ethereum block builders, including payments from another wallet involved in the exploit. Overall, the builders and the primary bot’s payout wallet retained approximately 59% of the vault’s lost assets.

The payments were made to secure favorable transaction ordering. Bitquery identified approximately 986 ETH transferred to builders, including 930 ETH from the dominant MEV bot. The available evidence does not establish that those builders knew the transactions were exploiting the vault.

The attack used a weakness in how sBOLD accounted for collateral temporarily held outside its BOLD balance. K3 Capital’s vault accepts Liquity’s BOLD stablecoin and distributes deposits across the protocol’s Stability Pools, allowing users to earn returns through sBOLD shares.

Bitquery reconstructed transactions involving flash loans, temporary deposits of wrapped Ether and repeated conversions between collateral and BOLD. The attacker could acquire vault shares while certain collateral was excluded from the share valuation, convert that collateral into BOLD and withdraw shares at a higher valuation.

The attack also exposed a discrepancy between early explanations and subsequent transaction-level analysis. Initial security alerts described a strategy involving attackers liquidating their own Liquity loans. Bitquery examined the relevant lending events and found no actual loan liquidations during the drain. Instead, the transactions involved collateral deliberately transferred into the vault.

A 2025 ChainSecurity audit had identified a related share-accounting weakness, although the audit recorded the issue as fixed in a later code version. Bitquery did not establish whether the vault deployed during the November attack used that corrected implementation.

And the original attackers did not get most of the money, not even close.

According to Bitquery, the wallet that initially deployed the attack contract and a second wallet it funded retained approximately $520,000. Investigators traced 162 ETH toward THORChain and another 129 ETH through Maya Protocol, where transactions requested Bitcoin payouts.

The participation of copycat bots resembles the UNCX Network exploit reported in October, when expanded blockchain investigations identified approximately $1.49 million in losses across four networks, including transactions attributed to automated and opportunistic attackers.

K3 Capital has confirmed its investigation and the contract pause, but a final incident report, verified recovery amount and compensation arrangements have not been publicly established in the reviewed disclosures.

Reental’s RNT Lend losses rise to $955,000 after investigation

A separate November 18 incident affected Reental’s RNT Lend platform on Polygon, where investigators identified unauthorized stablecoin transfers involving privileged contract-administration permissions.

Blockaid initially estimated the incident at $454,825, attributing the amount to transactions executed by two MEV bots. Bitquery’s subsequent reconstruction uncovered another $499,877 removed through transactions signed by an address holding Reental’s administrator privileges.

The revised total reached approximately $954,703, more than twice the amount in the original alert.

According to Bitquery, the incident began at approximately 11:39 UTC, when the privileged address deployed replacement smart contracts and changed the implementations underlying the platform’s USDT0 and USDC lending markets.

The replacement code allowed tokens to be transferred to an arbitrary recipient without an effective authorization check. Two MEV bots identified the opportunity and drained approximately $454,825 from the affected markets before the administrator-controlled address could execute its own withdrawals.

The bots got there first, and they got there by seconds.

After the initial attempt failed, the privileged address deployed another implementation with withdrawal permissions restricted to itself. Bitquery traced approximately $340,083 from 1,149 wallets associated with Reental’s wallet factory, alongside additional stablecoin withdrawals involving four Safe wallets.

Those transacions accounted for approximately $499,877, which subsequently moved through the Relay and Bridgers cross-chain services. Bitquery did not establish the final destination of the bridged assets.

The investigation also identified movements involving approximately $49.34 million in tokenized property assets. These tokens were transferred through administrative functions affecting lending collateral and Reental-controlled wallets.

Reental’s other authorized wallet signers subsequently used the platform’s token-management controls to retrieve the property tokens within approximately two hours. The $49.34 million valuation comes from prices assigned within Reental’s lending system, rather than independently verified market sale values.

So the property tokens came back, but the stablecoins were a seperate problem.

Bitquery’s analysis indicates that the USDT0 and USDC lending markets held approximately $10.01 million in lender deposits before the incident, against roughly $9.57 million in outstanding loans. The $454,825 taken by the bots represented the available stablecoin liquidity in those markets, not the entire outstanding loan book.

At the investigation’s final recorded snapshot, 16:17 UTC on November 18, the lending pool had not been paused. The researchers also identified malfunctioning deposit and withdrawal functionality, with the potential for additional assets sent into the affected markets to be removed through the altered contracts.

The incident shares an administrative-control dimension with the previously reported Hifi Finance governance takeover, in which an attacker reportedly used governance permissions to upgrade a contract and transfer user collateral. The mechanisms differed: Reental’s incident involved direct use of a privileged administrator address, while the Hifi case concerned control obtained through governance voting.

Bitquery established that the Reental transactions were signed using an address previously associated with the platform’s administration. The blockchain record cannot determine whether its private key was stolen, delegated or used by someone already holding authorized access.

Reental had not published a complete explanation when the investigation was released. The research team’s conclusions were based on November 18 blockchain records, and any subsequent remediation would require seperate verification.

Binance hacker-linked wallets move another $248 million in Ether

Meanwhile, wallets linked to Binance’s October 29 cryptocurrency theft transferred approximately 137,602 ETH, valued at $248.23 million, on November 19, according to blockchain monitoring service Lookonchain.

The movement represents the third consecutive day of substantial Ether redistribution associated with the attack, which resulted in approximately $6.3 billion in stolen digital assets.

On November 17, blockchain investigators identified approximately 74,880 ETH moving from attacker-linked wallets. Another 78,415 ETH was reported moving on November 18, followed by the November 19 transfers.

Combined, the three reported batches amount to approximately 290,897 ETH. Those figures measure cryptocurrency redistributed between addresses, rather than proceeds confirmed to have been sold or converted into other assets.

Blockchain transaction records show that the November 19 batch involved 12 transfers to separate recipient wallets, with eleven transfers carrying 12,000 ETH each and a final transfer of approximately 5,602 ETH.

The funds were recieved by new addresses, but those transfers alone do not establish completed laundering, Bitcoin conversion or cash withdrawals.

Earlier activity associated with the Binance theft included movements through cross-chain services. Blockchain analytics firm Elliptic identified approximately 2,100 ETH from the November 17 transfers that had been converted into Bitcoin, with subsequent activity involving CoinJoin transactions.

The latest movements also occurred during an expanding legal recovery effort.

On November 12, the US Department of Justice announced that authorities and private-sector partners had frozen more than $2.7 billion in assets associated with the Binance theft. The department said it had obtained court authorization to seize or restrain more than $1.2 billion of that amount.

US authorities attributed the October 29 incident to North Korean military hackers identified as TraderTraitor. The Justice Department said efforts to trace and restrict the stolen assets remained ongoing, including movements involving cryptocurrency bridges, exchanges and mixing services.

On November 18, Binance also disclosed that it had secured a worldwide freezing order valued at approximately $6.5 billion from the Abu Dhabi Global Market Courts.

As detailed in DaveFinances’ coverage of the Binance worldwide freezing order, the exchange said its legal advisers had identified approximately 26,000 wallet addresses potentially holding stolen assets.

The court order seeks to restrict the disposal of assets and support recovery proceedings. Its $6.5 billion value is not an additional theft, nor does it represent cryptocurrency already returned to the exchange. Likewise, the Justice Department’s $1.2 billion in court-authorized restrictions forms part of the broader $2.7 billion frozen amount.

Different wallets, but still the unanswered question of where the Ether finally ends up.

For the November 19 transfers, the observed activity establishes redistribution to new addresses rather than the completion of any particular disposal strategy. Investigators have identified some conversion activity in eariler batches, but that evidence cannot be extended automatically to the latest 137,602 ETH.

The two DeFi incidents and the Binance transfers also involve different financial measurements. K3 Capital’s estimated $3.42 million to $3.43 million represents assets drained from a vault, while Reental’s approximately $955,000 reflects stablecoins removed from lending markets and associated wallets. Binance’s $248 million figure describes a fresh movement of assets stolen during an earlier attack, not additional losses incurred by the exchange on November 19.

At K3 Capital, the unresolved accounting concerns the division of proceeds among attackers, bots and block builders, and whether any funds can be recovered. Reental faces unanswered questions about the use of its privileged administrator address, the security of its lending contracts and restoration of customer access. For Binance, the continuing movements show that a substantial amount of Ether linked to the October breach remains transferable despite court orders, wallet tracking and asset-freezing efforts targeting other portions of the stolen funds.

Editor-in-Chief at  | More Posts

Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.

Disclaimer: This content is for informational purposes only and does not constitute financial, investment, legal, or trading advice. Trading and investing involve risk. Read our full Disclaimer.