Arbitrum Freezes Hacker's ETH via System-Level Transaction

icon MarsBit
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
Arbitrum froze 30,766 ETH from the KelpDAO hacker using a system-level transaction. The action, executed via ArbitrumUnsignedTxType (EIP-2718 type 0x65/101), was injected by the Security Council through ArbOS. This involved state-level recovery, not a chain rollback. The attacker’s private key remains valid, but the ETH was directly transferred by the chain. The incident demonstrates Arbitrum’s contract security mechanisms in action.

Haseeb Qureshi, Managing Partner at Dragonfly, analyzed the freezing of 30,766 ETH belonging to the KelpDAO hacker on April 21, according to Huoxing Finance. He noted that this transaction type is ArbitrumUnsignedTxType (EIP-2718 type 0x65/101), a system-level transaction that cannot be signed by a standard EOA but can only be injected into ArbOS by the Arbitrum Security Council. This action did not involve a chain rollback or historical rewrite; functionally, it is a state-level recovery: the attacker’s private key can still sign transactions, but the ETH at that address has been transferred by the chain itself. This operation also demonstrates the Security Council’s authority under “catastrophic emergency” scenarios as described in Arbitrum’s progressive decentralization documentation.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.