Loading prices…
🩸BEARISH

sBOLD Vault Hack Sends $1.78M to Ethereum Builders

A copycat bot captured more than half the stolen funds but paid most of its proceeds to secure priority over rival transactions.

sBOLD Vault Hack Sends $1.78M to Ethereum Builders
sBOLD Vault Hack Sends $1.78M to Ethereum Builders
sBOLD Vault Hack Sends $1.78M to Ethereum Builders
sBOLD Vault Hack Sends $1.78M to Ethereum Builders

Attackers drained $3.4 million from K3 Capital's sBOLD savings vault in about eight minutes on Wednesday, exploiting its accounting to redeem shares at inflated values. Ethereum block builders received roughly $1.78 million as bots competed to have their transactions processed first, according to blockchain analytics firm Bitquery.

Bitquery traced 97 transactions tied to the exploit. One automated bot copied the attack and extracted $1.91 million, or 56% of the stolen funds, but paid most of its proceeds to builders.

Why it matters

The attackers repeatedly deposited BOLD and introduced wrapped ether that was initially excluded from the vault's accounting. They then converted the ether into BOLD and redeemed shares at inflated values, extracting other depositors' funds. The sequence could be repeated within a single transaction.

The vault pools BOLD, a token designed to hold a $1 value, and allocates deposits across Liquity lending pools to earn interest. Its loss highlights both the risks of vault accounting and the role of transaction-ordering competition, known as maximal extractable value, or MEV, in exploits.

Market impact

The $1.78 million sent to builders represents incoming payments, not confirmed profit. Builders also pay validators to publish blocks, and the analysis did not establish how much they retained. One block inclusion payment reached 44 ETH.

A CoinDesk review found that the original attacker and a wallet it funded ended up with about $520,000. ChainSecurity identified a self-liquidation vulnerability in a May 2025 audit and said it was mitigated in a later code version. It remains unclear whether the exploit involved that issue or whether the fixes were deployed.

Related tokens
$BOLD $ETH

Frequently asked questions

  1. How did the attackers extract funds from the sBOLD vault?

    They manipulated the vault's accounting by depositing BOLD, introducing wrapped ether that was initially excluded from accounting, and converting it into BOLD before redeeming shares at inflated values.

  2. How much did the copycat bot extract?

    The automated bot extracted $1.91 million, or 56% of the stolen funds, but paid most of its proceeds to block builders for transaction priority.

  3. Did Ethereum builders profit by $1.78 million?

    The figure measures payments received, not confirmed profit. Builders also pay validators to publish blocks, and the analysis did not establish how much they retained.

  4. How much did the original attacker and its funded wallet retain?

    A CoinDesk review of the transactions found that the original attacker and a wallet it funded ended up with about $520,000.

  5. Was the sBOLD exploit linked to the issue found in the 2025 audit?

    That remains unclear. ChainSecurity identified a self-liquidation vulnerability and said it was mitigated in a later code version, but it is unclear whether the attack involved that issue or whether the fixes were deployed.

Source attribution
Aggregated from CoinDesk · Verified · Last refreshed 1h ago
Open original →