An automated trading bot copied the attack that drained a $3.4 million vault run by K3 Capital, then walked off with more than half the money. The original exploit targeted the firm's sBOLD vault. Ethereum block builders, meanwhile, ended up with the largest single share of the proceeds — largely because the bot paid them most of its haul to get its transactions processed first.
The sequence is a familiar one in 2026: an attacker finds a flaw, and before the team can respond, someone else's script has replicated the same exploit against the same target. The difference here is how the money split. The bot didn't just skim — it out-earned the original thief by copying the attack and then spent the bulk of what it took on priority fees.
A copycat with better plumbing
The sBOLD vault was the target in both cases. The bot reproduced the attack automatically, with no evidence in the facts that it was manually operated or tied to the original attacker. Once it had the funds, it routed most of them to Ethereum builders as payment to be included first in a block. That's the same mechanism that keeps the chain running — validators and builders get to decide which transactions make it into a block, and how much a sender is willing to pay shapes that order.
In this case, the bot's willingness to hand over most of its proceeds is what pushed builders to the top of the payout list. The original attacker, the copycat, and the block builders all ended up with pieces of the same $3.4 million. The bot's share was more than half of the total — the largest cut any single party took, if you exclude the builders collectively.
Builders as the biggest winners
The headline number is the hack, but the structural story is the fee flow. A bot that pays most of its proceeds to get processed first is, in practice, working for the builders. That's not a glitch in the system; it's the system doing what it was designed to do. Priority ordering is a market, and the bot bid aggressively to win it.
Whether that bid made sense for the bot's operator is a different question, and one the facts don't answer. What's clear is that the builders captured the largest share of the $3.4 million, and the bot's operator kept less than half of what it stole. Copying a hack is cheap. Getting paid for it is where the costs pile up.
What's left for K3 Capital
K3 Capital has the sBOLD vault to account for, and a hack that was replicated before anyone could stop it. The facts don't say whether the vault has been paused, whether affected users have been made whole, or whether the team has traced any of the funds. Those are the open questions now — and the ones that will determine how much of the $3.4 million anyone actually recovers.
The bot's identity, its operator, and whether the original attacker and the copycat had any connection are all unknown. So is whether the builders will return any of the fees. Ethereum's block-building market doesn't have a refund mechanism built in, and the facts give no indication that one is being discussed.
What happens next depends on K3 Capital's next public statement, which hasn't come yet. Until then, the $3.4 million is spread across three parties, and the biggest slice sits with the builders who did what they were paid to do.




