Key Highlights:
- An automated copycat bot captured $1.91 million—56% of the total stolen funds—during an attack targeting sBOLD, surpassing the original attacker’s haul.
- Ethereum block builders collected approximately $1.78 million in incoming payments as the bot paid massive bribes, including 44 ETH in a single block, to outbid rival arbitrageurs via maximal extractable value (MEV).
- While a May 2025 ChainSecurity audit previously addressed a self-liquidation vulnerability in sBOLD, it remains unconfirmed whether Wednesday’s exploit involved that specific flaw or a separate accounting issue.
Automated MEV Bot Front-Runs Exploit on sBOLD Protocol
In a striking demonstration of competitive on-chain automation, an automated trading bot intercepted an ongoing decentralized finance exploit against sBOLD on Wednesday. The bot successfully replicated the original hacker’s transaction pattern, extracting $1.91 million in assets, representing roughly 56% of all funds compromised in the incident. However, rather than retaining the entirety of the windfall, the bot surrendered the vast majority of its gross take to infrastructure participants to ensure its transactions were confirmed before those of competing bots.
The sequence unfolded within Ethereum’s maximal extractable value (MEV) marketplace, a competitive environment where searchers, traders, and automated programs pay premiums to influence transaction ordering. To guarantee priority inclusion over other trading bots attempting to copy the same malicious payload, the bot engaged in an aggressive bidding war. On-chain data indicates that the race grew so fierce that payment for inclusion inside a single Ethereum block reached 44 ETH.
Block Builders and Validators Capture the Lion’s Share
As a result of the bidding escalation, specialized block builders received roughly $1.78 million in incoming transaction fees. This figure reflects gross incoming transfer volume rather than net profit, as builders must subsequently route a portion of their revenues to validators—the consensus nodes responsible for verifying transactions and proposing blocks to the Ethereum blockchain. The extent of the net profit retained by individual builders after compensating validators remains undetermined by available transaction analyses.
Meanwhile, the party that initiated the breach fared significantly worse financially than the network infrastructure operators who processed the transactions. According to a transaction review conducted by CoinDesk, the original attacker along with an associated wallet ended up with approximately $520,000—a total far smaller than the cumulative sums diverted to block builders during the MEV scramble.
Audit History and Codebase Vulnerabilities Under Scrutiny
The incident has drawn attention back to previous security evaluations of the affected protocol. Smart contract auditing firm ChainSecurity previously audited sBOLD in May 2025, during which researchers identified an attack vector that enabled unauthorized value extraction through a process of self-liquidations. At the time of the review, ChainSecurity noted that the vulnerability had been mitigated in a subsequent version of the smart contract codebase.
Despite that prior assessment, investigators have not yet confirmed the precise root cause of Wednesday’s exploit. It remains unclear whether the attacker leveraged an exploit path related to the previously documented self-liquidation issue, whether the audited security patches were never properly deployed to production, or whether the protocol was breached through an entirely separate accounting vulnerability.
Why This Matters
The dynamics of the sBOLD incident underscore the structural realities of public mempools and the sophisticated MEV architecture on Ethereum. When vulnerabilities are triggered publicly, generalized front-running bots and opportunistic searchers can identify, duplicate, and execute the underlying logic in seconds. Because priority is dictated by competitive bidding mechanisms, block builders and network validators often become the primary financial beneficiaries of on-chain exploits, extracting more capital than the hackers themselves while protocols bear the underlying losses.
Frequently Asked Questions
How much money was taken by the copycat bot versus the original attacker?
The automated copycat bot captured $1.91 million (56% of the compromised funds), but paid most of it away to ensure transaction priority. The original attacker and a wallet funded by the exploit retained approximately $520,000, according to a CoinDesk review.
Why did block builders receive $1.78 million during the attack?
The copycat bot competed against rival bots in the maximal extractable value (MEV) ecosystem. To secure top-of-block transaction inclusion, it paid enormous priority fees—including a 44 ETH fee in a single block—directly to block builders, who in turn share portions of those rewards with Ethereum validators.
Was the sBOLD protocol audited prior to the exploit?
Yes. ChainSecurity audited sBOLD in May 2025 and identified a self-liquidation vulnerability that it noted had been resolved in later code. However, it is not yet established whether Wednesday’s incident utilized that exact mechanism, if the updates were unapplied, or if an unrelated accounting error was targeted.




