THE DESK.Markets, in focus
crypto   News

Copycat bot captured over half the funds in $3.4 million vault hack

A copied exploit overtook the original attacker in K3 Capital’s sBOLD vault, while competing bots sent substantial payments to Ethereum block builders.

By The Desk Newsroom   ·   4 min read · Published

Updated

Editorial illustration for Copycat bot captured over half the funds in $3.4 million vault hack

A bot that copied an attack on K3 Capital’s sBOLD savings vault extracted about $1.91 million, more than half of the roughly $3.4 million drained on November 18. The bot also paid most of its proceeds to secure transaction priority, making the race to process the exploit a central part of the story. Blockchain analytics firm Bitquery traced 97 transactions that emptied the vault in approximately eight minutes.

The vault took deposits of BOLD, a token designed to maintain a value of $1, and deployed them across pools on the Liquity lending platform to earn interest. But sBOLD was a third-party K3 Capital product, not part of Liquity’s core protocol. Its design included adjustable components, among them a price oracle and a token-swap adapter, in contrast with Liquity V2 contracts described as unchangeable.

How the vault was exploited

Security firm Blockaid described an attack that began with a flash loan in wstETH and the liquidation of the attackers’ own Liquity V2 borrowing position. That sent debt and collateral into the platform’s stability pools. The attackers then minted inexpensive vault shares, swapped collateral and redeemed BOLD belonging to other depositors. The sequence combined activity on the lending platform with manipulation of how the separate vault accounted for its assets.

The accounting issue turned on the value assigned to the vault’s shares. Attackers deposited BOLD and introduced wrapped ether that was initially excluded from the calculation. They converted the ether into BOLD, then redeemed shares at inflated values. The sequence could be repeated within a single transaction, allowing attackers to extract funds supplied by other depositors. That mechanism explains how the vault’s reported share values became part of the exploit, rather than simply reflecting the assets deposited.

The copycat’s approximately $1.91 million extraction represented 56% of the stolen funds, according to a transaction review. That was substantially more than the approximately $520,000 ultimately received by the original attacker and a wallet funded by that attacker. The larger extraction was not the same as a comparable final gain for the bot: it spent most of the proceeds on payments intended to put its transactions ahead of competitors.

The competition for transaction priority

Bots competing to exploit the vault sent Ethereum block builders approximately $1.78 million in total. That figure covers incoming payments to builders across the competition, not a payment attributed solely to the copycat. It also should not be treated as the builders’ established profit. Builders pay validators to publish their blocks, and the available analysis did not determine how much of the incoming sum the builders retained after those payments.

Titan built most of the blocks containing the copycat bot’s transactions, while BuilderNet, Ultrasound and Quasar also processed transactions. Competition for inclusion pushed the payment for one block to 44 ETH. Those details show how the contest extended beyond copying the exploit itself: the bots also competed to have their transactions included ahead of others. The reported builder total, however, does not establish what each builder ultimately kept.

The attack was already underway when Blockaid issued an alert at 12:50 UTC on November 18. At that point, the security firm estimated that $3.43 million had been drained across roughly 34 transactions. That estimate was a snapshot and could have grown after the alert. An Ethereum record reviewed for one transaction flagged by Blockaid was timestamped 12:25 UTC, about 25 minutes before the alert, and contained 231 separate token transfers.

K3 Capital said at 13:08 UTC that it was investigating malicious activity involving sBOLD and had paused the contracts. That statement came 18 minutes after Blockaid’s alert. The company did not provide a loss figure in its statement, identify a cause or explain what depositors should expect. The pause was the response reported for the vault, while the loss estimates and transaction counts came from separate security and blockchain analysis.

There was also an earlier security review, although its relationship to this attack remains unresolved. ChainSecurity completed an sBOLD audit on May 19, 2025, and said an issue involving value extraction through self-liquidation had been mitigated in a later version of the code. The reporting did not establish whether the November attack used a related mechanism, whether those fixes had been deployed or whether a different accounting weakness was responsible.

Sources

CoinDesk: https://www.coindesk.com/tech/2026/11/19/ethereum-block-builders-received-the-most-in-a-usd3-4-million-vault-hack-data-shows Unchained via Yahoo Finance: https://finance.yahoo.com/markets/crypto/articles/k3-capital-pauses-sbold-contracts-163040777.html

Sources & reporting notes

  1. Ethereum block builders received the most in a $3.4 million vault hack, data shows
    CoinDesk · Reported Nov 19, 2026, 12:39 AM ET · Retrieved Nov 19, 2026, 10:15 AM ET
  2. K3 Capital Pauses sBOLD Contracts, Blockaid Says Attackers Have Drained $3.43M
    Yahoo Finance · Reported Publication date not specified · Retrieved Nov 19, 2026, 10:15 AM ET

For information only. Not investment advice. Investing involves risk, including loss of principal.

More crypto news →