1. Description
The incident highlights how attacks against developer endpoints and internal signing systems can lead directly to the compromise of cryptocurrency assets.
According to Binance's incident report, attackers used multiple stages of access and social engineering to compromise employees and obtain access to internal systems. The attackers subsequently leveraged compromised credentials and deployment permissions to reach wallet-signing operations.
The FBI's information referenced in Binance's report attributes the incident to the Democratic People's Republic of Korea (DPRK).
2. Technical Description
The attack involved a combination of developer endpoint compromise, credential misuse, unauthorized deployment activity, and blockchain transaction authorization abuse.
Key technologies and mechanisms involved:
EIP-7702: An Ethereum proposal that allows an externally owned account (EOA) to delegate execution to smart-contract code.
Hot wallets: Internet-connected cryptocurrency wallets used by exchanges for operational transactions.
Wallet-signing infrastructure: Systems responsible for authorizing and signing blockchain transactions.
Nonce manipulation: Attackers submitted multiple authorizations using sequential nonce values to increase the likelihood of one matching the wallet's current nonce.
Sweeper contract: Malicious smart-contract code designed to transfer assets from a compromised wallet to an attacker-controlled address.
The critical weakness was that an EIP-7702 authorization could remain active on-chain even after normal withdrawal services were suspended.
3. Attack Overview
The incident involved the following stages:
Initial compromise: A developer downloaded a tampered Homebrew installation while attempting to install an AI coding tool.
Social engineering: Another developer was targeted through a fake recruitment process and instructed to download a malicious coding assignment.
Internal access: Attackers used compromised developer systems and credentials to access internal tools and deployment permissions.
Signing infrastructure compromise: Malicious scripts and unauthorized deployment activity enabled attackers to reach wallet-signing operations.
EIP-7702 abuse: Attackers submitted 50 signed authorizations with different nonce values, attempting to delegate the targeted wallet to a malicious contract.
Asset transfers: The malicious sweeper transferred cryptocurrency from the compromised wallet to attacker-controlled addresses.
Continued unauthorized activity: Existing on-chain authorization allowed further transfers even after Binance initiated containment measures.
Response and recovery: Binance suspended withdrawals, worked with external partners to freeze assets, and executed additional transactions to revoke the malicious authorization.
4. Technical Analysis
A. Developer environment compromise
The attackers reportedly used two distinct entry points:
A tampered Homebrew installation downloaded by a developer in June 2026.
A malicious code repository delivered to another developer through a fake job interview in September 2026.
Binance's report describes malware that replaced a legitimate development-tool component with a malicious version, executed commands, and established communication with an external attacker-controlled server.
B. Abuse of internal credentials and deployment permissions
After compromising developer systems, attackers obtained access to credentials and a container deployment permission token. Binance reported that the attackers later accessed an engineer's computer, used stolen credentials, deployed a container, and triggered a malicious script.
This allowed the attackers to move from developer endpoint compromise toward the internal wallet-signing environment.
C. EIP-7702 authorization abuse
EIP-7702 enables an externally owned Ethereum account to delegate execution to smart-contract code.
In this incident, attackers used the compromised signing infrastructure to authorize a malicious sweeper contract. The authorization effectively gave attacker-controlled code the ability to move funds from the affected wallet.
The attackers submitted 50 authorizations using sequential nonce values. One authorization matched the wallet's current nonce and became active.
D. Persistent wallet control
Once the malicious delegation was established, the attacker could continue transferring assets without relying on Binance's normal withdrawal process.
This created a major containment challenge: suspending withdrawals and shutting down hot-wallet services did not automatically revoke an authorization already recorded on-chain.
Binance had to execute additional transactions to clear the malicious delegation.
5. Indicators of Compromise (IOCs)
The following blockchain addresses were identified in Blockaid's technical analysis. They are included as incident-related indicators, not as proof that every address is malicious in every context.
Indicator | Value | Context |
|---|---|---|
Attacker operator address |
| Address used to coordinate the attack |
Malicious sweeper contract |
| Contract used to sweep wallet assets |
Attacker collection address |
| Main destination for transferred assets |
Targeted Binance wallet |
| Binance 14 hot wallet |
6. Potential Impact
Financial loss: Approximately $6.34 billion in digital assets were reported as impacted.
Wallet compromise: Unauthorized access to hot-wallet signing operations enabled attackers to initiate transactions.
Persistent authorization abuse: Malicious EIP-7702 delegation allowed continued asset movement after normal withdrawal controls were suspended.
Operational disruption: Binance suspended withdrawals and undertook additional containment and recovery actions.
Developer security exposure: The incident demonstrated how compromised developer devices, software downloads, and recruitment-based social engineering can affect critical financial infrastructure.
Industry-wide risk: Other cryptocurrency exchanges and custodians using similar signing and wallet architectures may face comparable risks.
7. Recommendations
Immediate Actions
Review all wallet-signing activity for unauthorized transactions and unexpected EIP-7702 authorizations.
Inspect hot wallets for unexpected delegation code or changes in account execution behavior.
Revoke unauthorized on-chain delegations using a tested recovery procedure.
Rotate potentially exposed credentials, API tokens, deployment tokens, and signing permissions.
Isolate compromised developer endpoints and investigate suspicious software installations.
Monitor suspicious transfers, new destination addresses, and unusual transaction bursts.
Preventive Measures
Secure developer environments: Enforce endpoint detection, application allowlisting, and software-source verification.
Strengthen recruitment security awareness: Train employees to identify malicious interview invitations, coding assignments, and repository downloads.
Protect signing infrastructure: Isolate signing systems and enforce least-privilege access.
Implement transaction simulation: Inspect and simulate transactions and authorization lists before signing.
Enforce transaction policies: Apply destination allowlists, transaction-value limits, and approval requirements.
Deploy emergency controls: Maintain a tested kill switch to pause signing, isolate wallets, and stop wallet refills.
Monitor on-chain behavior: Alert on unexpected wallet code changes, unusual authorization activity, and large transfers to newly created addresses.
Test incident response: Regularly rehearse wallet isolation, authorization revocation, credential rotation, and asset-freezing procedures.
8. Conclusion
The Binance incident demonstrates how compromising developer environments and internal signing infrastructure can lead to large-scale cryptocurrency theft. By abusing EIP-7702 authorization, attackers established persistent control over a hot wallet and bypassed normal withdrawal safeguards.
The incident reinforces the need for stronger developer security, protected signing systems, transaction-level policy enforcement, and continuous on-chain monitoring. Cryptocurrency organizations must ensure that emergency response mechanisms can revoke malicious authorizations—not simply suspend normal transactions.
