Binance suffered an EIP-7702 authorization attack involving more than $6 billion in assets, while multiple BTCPay Server instances had their hot wallets compromised, with officials advising immediate server shutdowns.
Latest Developments
Security risks in the crypto industry have recently come into sharp focus. Disclosed information shows that Binance suffered an EIP-7702 authorization attack involving more than $6 billion in assets. At the same time, hot wallets of multiple BTCPay Server instances were stolen, and officials advised immediately shutting down servers. Both incidents involve fund security and authorization processes, with the Binance incident drawing market attention due to its involvement of a leading exchange and the relatively large scale of assets.
Key Facts of the Two Incidents
Binance is a leading exchange, and the EIP-7702 authorization attack involved more than $6 billion in assets. Relevant information indicates that the incident involves a huge scale of assets and affects exchange reserves and market confidence. BTCPay Server is an open-source payment tool. In this incident, hot wallets of multiple instances were stolen, involving the fund security of merchants and self-hosted users, and officials have advised immediately shutting down servers. The two incidents point to authorization attacks and hot wallet theft respectively, both posing direct challenges to user fund security and platform security management.
Key Focus of the Binance Incident
Based on disclosed information, the core facts of the Binance incident include the EIP-7702 authorization attack, assets involved exceeding $6 billion, and the incident's impact on reserves and market confidence. As Binance is a leading exchange, market attention is focused on the scale of assets involved, reserve security, and changes in confidence. Currently confirmable information centers on the attack type, the scale of assets involved, and the impact level. More details on attack paths, the number of affected accounts, and asset recovery still need to be based on further disclosure. For exchanges, authorization management and reserve transparency are important dimensions for observing the subsequent impact of the incident.
User Impact of the BTCPay Incident
Key facts of the BTCPay Server incident include the theft of hot wallets across multiple instances, official advice to immediately shut down servers, and the fund security risks faced by merchants and self-hosted users. Unlike centralized exchange incidents, this incident more directly affects merchants and self-hosted users using open-source payment tools. The official shutdown advice means that affected users need to prioritize handling hot wallet risks and pay attention to subsequent security updates and handling guidance. Current public information has not disclosed details such as the stolen amount or the number of affected instances, and the relevant scope of impact仍需持续观察.
Transmission of Security Risks and Market Attention
The two incidents jointly reflect the security challenges of crypto assets in authorization management and hot wallets. Due to the involvement of a leading exchange and a relatively large scale of assets, risk attention for the Binance incident is concentrated on reserves and market confidence. The BTCPay Server incident is concentrated on the fund security of merchants and self-hosted users, as well as the instance security of open-source payment tools. Although they are independent incidents, both show that authorization attacks and hot wallet theft can directly affect fund security and trigger user attention to platform security architecture, emergency response, and transparency of information disclosure.
Follow-Up Areas to Watch
Going forward, attention should be paid to the investigation progress of Binance's EIP-7702 authorization attack, the handling of assets involved, and changes in exchange reserves and market confidence. Attention should also be paid to the implementation of official shutdown advice in the BTCPay Server hot wallet theft incident, the handling of fund security for merchants and self-hosted users, and adjustments to relevant security architecture. Security incidents in the crypto industry have emerged in a concentrated manner, and authorization attacks and hot wallet risks remain key areas requiring continued observation.
