A Bot Named 'Yoink' Just Stole $7.7M From a Hacker Before Kelp Could Blink

A Bot Named 'Yoink' Just Stole $7.7M From a Hacker Before Kelp Could Blink

An MEV bot called "Yoink" intercepted a live exploit in real time, front-running an attacker and capturing $7.7 million in rsETH before the hacker could pocket a single dollar.

This is not a drill. Someone tried to drain a custom Safe module on Kelp's protocol, and instead of walking away rich, they got robbed by an automated sandwich bot operating faster than any human could react. Kelp then temporarily froze the receiving address, but by that point the funds were already sitting in Yoink's wallet, not the attacker's.

What Actually Happened

The attacker targeted a vulnerability in a custom Safe module, a smart contract configuration used to manage multi-sig wallets. The exploit was designed to redirect rsETH, Kelp's liquid restaking token, to an address the attacker controlled.

The problem? MEV bots watch every pending transaction in the mempool. Yoink spotted the exploit transaction before it was confirmed, copied the logic, paid a higher gas fee, and executed first. The attacker's transaction landed second, finding nothing left to steal.

Kelp moved quickly after the fact, freezing the destination address to limit further damage. But the freeze came after Yoink had already won the race.

Why This Should Make Every DeFi User Uncomfortable

Yoink's intervention looks like a happy accident. The funds did not return to users. They did not go to a white-hat recovery address. They landed in the MEV bot's wallet, which means $7.7 million in rsETH is now sitting somewhere outside both the attacker's and the protocol's control.

This is the uncomfortable reality of public blockchains. MEV bots do not care about your money. They care about profit. Yoink accidentally prevented a theft, but there is no mechanism forcing it to return the funds. Whether those assets ever make it back to Kelp or its users depends entirely on who controls that bot.

Custom Safe modules have been a persistent attack surface across DeFi. When protocols build custom logic on top of audited infrastructure, they introduce new risk layers that audits may not fully cover. This exploit is another reminder that complexity is the enemy of security.

What to Watch

If you hold rsETH or interact with Kelp's protocol, monitor official channels for updates on whether the $7.7M is recoverable and whether the vulnerability has been patched. The frozen address buys time, but it does not resolve the exploit.

More broadly, this event signals that MEV infrastructure is now fast enough to compete with attackers in real time. That is either the most chaotic form of DeFi protection imaginable, or a preview of a new class of opportunistic bot behavior that protocols have no defense against.