Morning Edition · Saturday, November 21, 2026Published at 12:48 AM EST · New York
The three failures were in a token approval, a liquidation path and a cloud credential, all outside the core contract code that audits usually review.

K3 Capital, Ethereum, about $3.43 million. On November 18, Blockaid flagged an active drain of K3 Capital's sBOLD vault, which holds BOLD, the stablecoin issued by the Liquity V2 lending protocol. Early reports blamed a self-liquidation in Liquity V2 funded with flash-borrowed wstETH. K3's postmortem, based on analysis by the security firm ChainSecurity, gave a different cause. It said the attacker used an unused 1inch router approval that the vault still held, and it said neither Liquity V2 nor 1inch was exploited. The loss was about 3.43 million BOLD, nearly all of the vault's assets. K3 paused the vault at 13:05 Coordinated Universal Time, offered a 15% bounty and said it would work with law enforcement. It has not yet counted losses to users who held the vault token through Pendle. DeFiHackLabs published its reproduction of the attack as a "swap-verification drain", which it later updated. That label fits K3's account of a flaw in how the vault checked swaps sent through the old approval. No attacker has been identified.
MORE Markets, Flow's Ethereum Virtual Machine (EVM) network, about $308,000. Starting at about 17:30 Coordinated Universal Time on November 16, an attacker used a flash loan to open a position in the market that pairs ankrFLOW (Ankr's liquid staking token for FLOW) with wrapped FLOW (WFLOW). This market runs in e-mode, which allows higher borrowing against closely correlated assets. The attacker then liquidated the position. The protocol's logic cleared the collateral without settling the matching WFLOW debt, which left WFLOW free to withdraw. Blockaid put the loss at about $308,000. MORE paused the protocol, Ankr suspended ankrFLOW, and the Flow Foundation said the core network was not affected. This is MORE's second loss through the same pairing. On August 31, Blockaid reported that an attacker used the Ankr token and e-mode to drain about $9.3 million in WFLOW. DeFiHackLabs has published a reproduction of the November attack.
Initia, about $3.27 million. Initia, a layer-1 network that hosts its own rollups, said an attacker got into its infrastructure on November 9 through command injection. The attacker used a compromised Google Cloud key that Initia used to provision private nodes. With that access, the attacker approved forged Inter-Blockchain Communication (IBC) withdrawals from five rollups. About $3.27 million moved, and Initia says about $2.16 million is now frozen. The chain has been halted since November 10. Three weeks earlier, a bug in the script cache of Initia's MoveVM let an attacker mint tokens and take about $2.7 million. Initia says a patch is under audit, and Rekt News has written up both incidents. Separately, the Polygon real estate tokenization platform Reental reported a loss of about $454,000 on the same day as the K3 drain, without giving a cause.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
What this means
These losses came from privileges that protocols had granted and then forgotten, a router approval, a liquidation path, a cloud key, exposing vault curators and appchains whose audits stop at contract code. Expect curated vaults to revoke old approvals and publish operational audits within months, a pattern a run of code-only exploits would contradict.
What to watch
Observations to monitor, not financial advice.
Synthesized from: DeFiHackLabs · DeFiHackLabs · DeFiHackLabs · Rekt News
Comments
0No comments yet.