
Aave Challenges New York Restraining Notice on $71M in Frozen ETH Tied to Kelp DAO Exploit
Aave LLC has asked a New York federal court to vacate a restraining notice targeting roughly $71 million in ETH frozen by Arbitrum's Security Council after the April 18 rsETH exploit. The company argues the recovered funds belong to victims of the attack, not to creditors pursuing North Korea-linked judgments.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
The Motion
Aave LLC filed an emergency motion asking a court in the Southern District of New York to vacate a restraining notice that reaches approximately $71 million in frozen ETH. According to the filing, the notice was served on Arbitrum DAO on May 1, and Aave asked for an expedited hearing and a temporary vacatur. The company argues the assets were designated for user restitution and should not be subject to outside claims.
How the Funds Were Frozen
The ETH at issue was frozen by Arbitrum's Security Council on April 21, three days after the Lazarus Group stole roughly 116,500 rsETH from Kelp DAO's LayerZero bridge. The council used its 9-of-12 emergency powers to move 30,765 ETH without the attacker's key and designated it for a recovery pool. Aave's April 24 funding update put the original backing shortfall at 163,183 ETH. Kelp's own freeze, Arbitrum's action and expected Aave liquidations together closed about 52.9% of that gap. DeFi United assembled more than $300 million in commitments for the remainder, including a Mantle credit facility of up to 30,000 ETH and a request for 25,000 ETH from Aave's treasury.
The Legal Theory and Its Limits
The plaintiffs' theory, as described in the reporting, rests on attributing the exploit to Lazarus Group and on prior judgments tied to North Korea. Aave's motion contests the step from alleged attacker control to lawful ownership, arguing that stolen assets do not become attachable property because a thief briefly held them. The motion also contends that Arbitrum DAO is not a juridical entity capable of being served. That second point is contested terrain: US courts have treated DAOs as general partnerships or suable collectives in earlier cases involving bZx, Compound-related litigation and, more recently, Lido DAO. The service plan in the filing included posting on Arbitrum's governance forum and mailing copies to the legal entities behind the DAO, Security Council members and large ARB holders, with a warning that noncompliance could carry legal consequences for governance participants.
Governance Exposure and Protocol Precedent
Travers Smith's analysis of the Kelp episode, as cited in the coverage, locates reachability in governance structure and demonstrated control. On that reading, Arbitrum's exposure stems from a documented emergency-action mechanism that was actually exercised. Delegates on Arbitrum's forum were already asking about indemnification, defense-cost advancement and litigation exposure before the motion was filed. The episode also shows that large protocols will override immutability when losses are severe enough, a capacity that helped users here but leaves a governance record that outside claimants can read. The outcome could shape whether protocols are willing to intervene during future hacks, even where they have the technical ability to protect users.
What Remains Open
The sources do not report a ruling on the emergency motion. Coverage describes the dispute as a test of whether recovery funds return to users first or become available to outside creditors, but the court has not yet indicated how it will treat the ownership and entity-service questions.
Why It Matters
For Traders
Any ruling that restrains frozen ETH on Arbitrum could affect the timing of victim restitution, so watch for an expedited hearing date in the Southern District of New York.
For Investors
The case may set a precedent on whether DAO-held recovery funds are reachable by outside creditors, which bears on governance risk across DeFi protocols.
For Builders
Emergency powers that are documented and exercised can become discoverable evidence of control, so teams should review how such mechanisms are scoped and recorded.
This article is for information only and is not financial advice. Read the full disclaimer.






