Is rsETH "tampered with"? Hacker: I was just doing a stress test (and took some assets along the way)

This rsETH attack incident, to put it simply, is a classic story in the DeFi world: the code looks very stable, but in reality, it's quite "flexible." From the current progress, the issue is most likely a combination vulnerability of contract logic and external calls, caught by the hacker through "time gaps + permission boundaries" and exploited.
The good news is that the project team responded relatively quickly: immediately pausing relevant modules, investigating fund flows, and collaborating with security agencies for on-chain tracking. The bad news is that once user confidence is shattered, it’s very hard to repair immediately.
The market impact of such events usually occurs in three steps:
First, panic selling;
Second, emotional recovery;
Third, selective forgetting (yes, the market’s memory is really poor).
Looking ahead, if the recovered funds ratio is high and the compensation mechanism is clear, prices are likely to recover; otherwise, it may enter a "long-term trust discount period."
What can investors learn? One sentence: don’t just look at APY, check if the "code has vulnerabilities." #美伊谈判陷入僵局