Site menu
Back to news

ImportantPANews

Crypto.com CEO: The Platform Is Unaffected by the Binance Hack Incident and Is Blocking Related Addresses

Crypto.com CEO Kris Marszalek stated that Crypto.com is not affected by the Binance cybersecurity attack. The platform is operating normally and all user funds are secure. The Crypto.com team is actively blocking addresses associated with this hack incident and has contacted Binance to offer assistance.

  • #Hack

More flash news

View all

Binance: Total Verified Frozen Amount Stands at Approximately $3 Billion

Binance released an update stating that the current total verified frozen amount is approximately $3 billion. The Binance team is working closely with law enforcement agencies, issuers, blockchain intelligence firms, and industry partners to continue tracing and freezing additional assets. Binance noted that it will only publish confirmed figures, and will provide further updates as more verified information becomes available, emphasizing that user funds remain safe.

Analysis: The Hacker Behind This Binance Hot Wallet Attack Is Suspected To Be The Same Group That Previously Attacked Kelp DAO

Per on-chain analyst monitoring, the hacker that carried out this attack on Binance's hot wallet is suspected to be the same group that previously targeted Kelp DAO. 30 minutes ago, the Binance hacker transferred all 74.56 million ARB to address 0x0000000000000000000000000000000000000DA0, which is tagged by Arkham as the Kelp DAO Hacker. These tokens have not been transferred or sold as of yet. Kelp DAO was attacked on April 18 this year, incurring losses of approximately $292 million worth of rsETH, and the community at the time suspected the North Korean hacking group Lazarus Group was responsible.

SlowMist Yu Xian: The EIP-7702 Mechanism Has No Flaws; The Binance Hacker Only Leveraged It to Achieve Bulk Token Theft

The technical clarification for the recent Binance-related hot wallet token theft incident has been officially released<p>SlowMist founder Yu Xian explicitly stated that the Ethereum EIP-7702 mechanism itself has no security issues. The core purpose for the hacker to select this mechanism in this attack is solely to simplify the operational process of bulk sweeping tokens from Binance-associated hot wallets.</p><p>On-chain retrospective data shows that the hacker's overall operation logic is relatively crude. Before launching the actual token theft, the hacker spent several hours conducting drills and preparations for related operations, and did not complete the attack by exploiting native vulnerabilities of EIP-7702.</p><p>Yu Xian also emphasized that even without the EIP-7702 mechanism, this hacker group could fully complete similar token theft operations through other existing technical paths. The root risk of this incident is not a design flaw in the Ethereum mechanism itself.</p>

Blockaid CEO: Binance Hack Incident Likely Stemmed From Compromised Signing System, Not Private Key Theft

In response to the recent Binance hacking incident, a relevant lead from a security firm has disclosed preliminary speculation on the attack path. <p>Blockaid CEO Ido Ben-Natan pointed out that the core cause of this attack is most likely a compromise of the platform's signing system, rather than the direct theft of private keys from the exchange's cold/hot wallets as previously speculated by external parties.</p><p>The attacker's specific operational method is suspected to have bundled 50 EIP-7702 authorizations into a single transaction, taking over Binance-related wallets through this method and subsequently transferring assets.</p><p>As of now, Binance has not issued an official confirmation announcement regarding specific technical details of this attack or the actual scale of losses. The full investigation of the incident is still ongoing. Users are advised to remain vigilant against the spread of related false information and conduct proper security verification for their own assets.</p>

Crypto.com CEO: The Platform Is Unaffected by the Binance Hack Incident and Is Blocking Related Addresses | CoinByte