K3 Capital’s Ethereum Vault Drained of $3.43M in Reported Exploit
Key Highlights
- Blockaid detected approximately $3.43 million drained from K3 Capital’s sBOLD vault across 34 transactions on November 18.
- The exploit involved flash-loaned wstETH, manipulated Liquity V2 liquidations, and unauthorized withdrawals of pooled BOLD, according to Blockaid.
- Blockaid identified multiple addresses linked to the incident, including the suspected exploiter and the affected vault.
Blockchain security firm Blockaid detected an exploit targeting K3 Capital’s sBOLD vault on Ethereum on November 18, 2026.
In an X post, the security firm said approximately $3.43 million was drained from the vault across roughly 34 transactions. The attack was still ongoing when Blockaid issued its initial alerts.
sBOLD is an ERC-4626 vault developed by K3 Capital that accepts deposits of BOLD, the stablecoin issued by Liquity V2, and allocates them across Liquity V2 stability pools. Depositors receive sBOLD shares that represent a pro-rata claim on the underlying positions and associated yields from interest and liquidation activity.
How the exploit unfolded
According to Blockaid, the attackers used flash loans to borrow wstETH before self-liquidating a Liquity V2 trove into the stability pools. They then minted sBOLD shares at a reduced cost, swapped the received collateral, and redeemed BOLD belonging to other depositors. The sequence allowed the extraction of value from the vault’s pooled deposits.
Onchain Lens independently reported a similar loss figure and described the use of borrowed funds to manipulate liquidations and withdraw more BOLD than the attackers’ own deposits justified. Monitoring of related addresses showed limited subsequent movement at the time of the reports.
Blockaid identified several addresses connected to the incident, including an address labeled as the suspected exploiter at 0xDC0e2FDEb89D2F363F2EA1B50E923d464C414dAA, a helper address at 0x19Ad153B83f9a1cbCAc2182DcEf14D0E825A9634, and the victim vault at 0x50Bd66D59911F5e086Ec87aE43C811e0D059DD11.
K3 Capital subsequently commented on the incident. In an X post, the firm said, “We are investigating malicious activity involving sBOLD. Contracts have been paused.”
The Crypto Times reached out to K3 Capital for comment on the matter but did not receive any at the time of this publication.
The sBOLD incident adds to a series of security events involving Ethereum-based infrastructure and protocols this year.
On October 29, attackers compromised signing infrastructure and used the EIP-7702 delegation mechanism to convert a Binance hot wallet into a sweeper contract. According to Binance, the multi-chain operation was estimated at roughly $6.3 billion in total value affected, with approximately $2.85 billion in stablecoins and assets frozen by issuers and networks. Nearly 75,000 ETH, valued at about $137 million at the time, was later moved across wallets in mid-November.
On May 18, a Verus–Ethereum bridge exploit was attributed to missing source-amount validation in the bridge’s Solidity logic rather than a key compromise, resulting in the drainage of $7.54 million.
Blockaid’s H1 2026 report identified smart contract and code-level exploits as the leading category of Ethereum incidents in the first half of the year. Privileged key compromises, including those affecting Humanity Protocol and StablR, and isolated user errors such as those observed on CoWSwap also contributed to the total.
These incidents involved different attack methods, ranging from infrastructure compromises to protocol vulnerabilities and transaction-approval mistakes.
Defensive measures and other developments
Security initiatives have also focused on reducing risks associated with transaction approvals. The Ethereum Foundation and ecosystem partners stated that they continued work on ERC-7730 and Clear Signing tooling intended to replace blind signing with human-readable transaction descriptions to make transaction approvals safer on Ethereum.
The initiative aims to help users understand the actions and permissions associated with a transaction before approving it. This is intended to reduce the risk of users unknowingly authorizing malicious transactions.
Also Read: Etherscan Reports Unauthorized Access Attempts on Support System
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


