Trail of Bits releases security hardening guide for wallet signing systems
Understand this story
Trail of Bits released a checklist for wallet signing systems in response to a Binance security incident in October 2026. The organization said attackers obtained valid signatures through EIP-7702 delegation and repeatedly moved funds without extracting private keys. The checklist requires teams responsible for wallet infrastructure to map the services and APIs that can request signatures, treat delegation as an administrative permission, use separate custody controls to limit losses after a signing compromise, and monitor wallet permission changes. Trail of Bits said systems that have not updated their detection rules may miss malicious permission changes and asset transfers.
AI overview based on source reports · Updated 1 hr ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Trail of Bits BlogAfter Binance, check what your signing systems can approve
This article examines the October 2026 Binance security incident, in which attackers who compromised a DevOps laptop obtained valid signatures from Binance's wallet-signing service and used an EIP-7702 delegation to authorize repeated transfers without further signatures. It argues that transaction execution and monitoring systems must understand newer Ethereum execution paths such as EIP-7702 delegations, session keys, Safe modules and ERC-4337 UserOperations, and offers a four-step checklist covering reduced signing access, treating delegation as an administrative privilege, limiting damage if signing is compromised, and detecting changes in wallet authority.
Activity for this story
Not enough continuous observations to show a trend yet.