The October 2026 security breach involving Binance raises critical operational questions for all organizations managing user funds. Specifically, can your security systems detect when a legitimate signature enables an attacker to gain wallet access? If an organization focuses solely on monitoring transfers and ownership changes, it may overlook the transfer of wallet authority until assets are moved.
Binance's initial update regarding the incident indicated that unauthorized withdrawals were made possible through a compromised DevOps laptop that granted an attacker access to a service container. A subsequent report confirmed further breaches but found no indication of wallet private key leaks. In its November 3 report, Binance detailed a more extensive attack that included social engineering tactics, misuse of an internal AI tool, stolen credentials, and unauthorized access to its wallet-signing service. The attacker managed to obtain valid signatures, underscoring a significant risk: a compromised server capable of requesting signatures can exploit a protected key without needing to extract it.
The attacker utilized an EIP-7702 delegation that allows a wallet to issue a standing instruction.
“Use this code when my account is called.”
This instruction remains in effect until changed or cleared using the wallet’s key. Consequently, this enabled multiple transfers, including funds deposited after the initial theft, without requiring further signatures from Binance. Additionally, other Binance wallets were compromised through standard signed transfers.
To maintain effective transaction execution and monitoring systems, they must adapt to Ethereum's evolving landscape. EIP-7702 authorizations fall outside the scope of ordinary calldata. Components such as session keys, recovery pathways, authorization modules, Safe modules, and ERC-4337 UserOperations introduce additional execution paths that signing policies and monitors need to comprehend. Systems that have not been updated may overlook harmful authority shifts and asset migrations, leaving wallets vulnerable. Security teams must revise their detection protocols and ensure these potential attack vectors are adequately covered.
If you oversee the security of wallet infrastructure, begin with the following checklist.
Four steps to enhance wallet security
The following four recommendations address the vulnerabilities exposed by the attack. Tests are also included to verify the effectiveness of these security measures.
1. Limit access to signing infrastructure
Document every service and API that can request wallet signatures, who has access, and what it can authorize, including transfers, delegation, and arbitrary data. Regularly review this inventory whenever wallet functionality changes on supported chains. It is essential to separate signing infrastructure from routine business systems and confirm transaction details through an independent system. Implement our TRAIL method to trace how a compromised laptop or server might interact with signing.
Verify the result:
- For each identified compromise path, use the access and credentials of the compromised system to attempt an unauthorized action. Identify the expected control to block it and retain evidence that no valid signature was generated.
Configure signing services to identify requests that modify account authority. Reject EIP-7702 authorizations for custody externally owned accounts (EOAs) that do not require delegation, ensuring that generic digest-signing APIs cannot bypass this restriction. Where delegation is necessary, separately approve the authorizing account, delegate address and code, chain, and nonce. Simulations must apply the proposed delegation and inspect changes to permissions and future execution authority alongside immediate balance changes before execution is evaluated.
-
Requests for delegation from accounts with delegation disabled should be rejected through both dedicated and generic signing interfaces.
-
Changing an approved account, delegate, chain, or nonce should necessitate renewed approval. Simulations should reveal any added authority, even if the transaction does not involve immediate asset movement.
3. Mitigate risks even if signing is compromised
Even after delegation, the original EOA key can still transfer funds or modify the delegate. If the key is compromised, an attacker could bypass limits set by the delegate. Safeguard those assets with separate custody controls that the operational key cannot alter. Our cold-storage guidance outlines independently enforced limits, monitored delays on sensitive actions, and a separate configuration authority.
-
Treat the operational key as if it were compromised and attempt direct transfers, delegate replacement, and policy modifications. Confirm that these actions cannot bypass the claimed protections, including shortening or eliminating delays.
-
Conduct incident response drills against a malicious withdrawal. Record alert and containment times, and demonstrate that responders can cancel or contain the withdrawal before it is executed. Ensure that the blocked withdrawal cannot execute subsequently.
4. Detect alterations in wallet authority
Map each wallet to the assets and contracts it manages, including wallets that currently hold no funds. Alerts should identify affected systems and privileges (e.g., unapproved delegation on an account that can upgrade funded vaults). Track direct calls, module executions, and ERC-4337 operations back to their authorization paths.
-
Test various delegation scenarios, mixed authorization tuples, multisig-module execution, and failed UserOperations within successful bundles.
-
Monitoring should reconstruct authority changes and asset movements in sequence, identify affected systems, and differentiate detection from controls that prevent execution prior to fund movement.
Make signing infrastructure a continuous responsibility
If your organization operates wallets or signing services, reassess their security measures. Test whether your signing policies accommodate EIP-7702 and ERC-4337, whether independent safeguards remain effective if an attacker gains access to signing, and whether your monitoring effectively detects changes to accounts and permissions.
Assign someone to oversee this review and establish a regular schedule. Reassess whenever you modify the protocols you support, the wallets you utilize, or your signing services.