News linked to both this project and an event.
According to market sources, the U.S. Federal Bureau of Investigation (FBI) has stated that it is aware of the hack attack on Binance and is currently in communication with relevant partners to understand the scope of the attack and assess its potential impact.
Odaily report: Crypto analyst Darkfost posted that although Binance yesterday suffered an attack suspected to be linked to the North Korean hacker group Lazarus Group, with losses of approximately $6.3 billion—the largest theft in crypto industry history—the platform's reserve assets only declined modestly, and the impact on users appears limited.Data shows that during the attack, Binance saw outflows of 18,279 BTC, 185 million XRP, and $1.67 billion USDT at one point; ETH flowed out in two batches, totaling 246,840 coins (167,464 and 79,376 respectively). Based on same-day reserve changes, BTC reserves fell 3.1% to over 682,000 coins, ETH dropped 8.5% to 3.3 million coins, XRP declined 8% to 2.47 billion coins, and USDT decreased 6.3% to $34.1 billion.Additionally, Binance stated it has frozen approximately $3 billion in related assets, including $1.567 billion USDT and over $800 million USDC, and pledged to absorb losses through the SAFU fund and company reserves. Darkfost believes the magnitude of change in Binance's reserve assets indicates the platform still possesses a certain capacity to absorb shocks.
Odaily reports: Liquid Capital founder Yi Lihua posted on X platform, stating: "We repeatedly called for a pullback every day, but never expected the strong support level of $79,000 to be broken by a black swan event. This was not part of the plan. The originally planned $75,000 and $71,000 levels need to be re-observed and adjusted due to changed circumstances. However, the end of the black swan impact and the midterm elections marks the arrival of the best opportunity to buy the dip."
A Binance spokesperson told Cointelegraph that it is investigating a potential security issue with an Ethereum wallet. The security team is reviewing related activities, and no impact on user funds has been confirmed at this time.
Illia Polosukhin stated that the attack involving approximately $3.8 million only affected USDT on BSC. NEAR Intents and near.com are now back online, and affected users will receive full compensation.
Ethena founder Guy Young stated that USDe backing assets currently have no direct exposure to stETH or other liquid staking tokens, and he expects this incident will not impact Ethena.
Odaily Odaily A new study by the Cambridge Centre for Alternative Finance reveals that approximately 31% of Ethereum node activity is located in the United States, with another 39% distributed across EU countries excluding the UK, indicating that the geographic distribution of Ethereum nodes remains relatively concentrated in Western nations.Lead researcher Alexander Neumuller stated that while node distribution is not currently concentrated in any single country, it is heavily reliant on a few major cloud service providers, including Hetzner, Amazon AWS, and OVH. Notably, the Ethereum network does not require half of its validators to fail for problems to arise. If more than one-third of validators go offline simultaneously, the network may be unable to finalize block checkpoints (finalization). Neumuller pointed out that nodes and validators do not have a one-to-one correspondence; a single node may run multiple validators. Therefore, it is currently impossible to precisely assess the actual impact on the validator network from the failure of a specific node or service provider.Furthermore, the study reassessed the energy consumption of Ethereum following The Merge. Data shows that Ethereum's current annual energy consumption is approximately 7.9 GWh, equivalent to a continuous power draw of about 1 MW. This represents only about 0.02% of pre-merge levels, a reduction of approximately 99.98%. Currently, over 56% of the energy used by the Ethereum network comes from sustainable sources, exceeding the global average.The study also noted that client software diversity is another potential risk. If a dominant client software has a vulnerability, it could affect a large number of network participants. The report was published by the Cambridge Centre for Alternative Finance and supported by the Ethereum Foundation. (The)
Wasabi Protocol stated that the Wasabi smart contracts on Solana are secure and unaffected by this vulnerability. The vulnerability is limited to Wasabi’s EVM deployments. The team is collaborating with leading security firms and has contacted law enforcement and the FBI. Further updates will be shared as they become available.
Lido has released an update regarding the Kelp security incident, stating that its Earn-series vaults are working with the management team to address the issue, focusing on two key risk areas: rsETH exposure and tightening liquidity in lending markets. Lido emphasizes that its core staking protocol remains unaffected, and both stETH and wstETH remain secure and stable. Currently, only the EarnETH vault holds approximately 9% of its TVL in rsETH exposure; related deposits and withdrawals have been suspended by the management team pending resolution. Of the ~$70 million in ETH stolen in the earlier attack, roughly $70 million has already been recovered; asset recovery and loss allocation efforts are ongoing. To mitigate liquidity pressure, the management team has reduced leverage and optimized position structures, significantly decreasing wETH debt exposure. Should losses ultimately materialize, EarnETH will activate its $3 million “first-loss protection mechanism,” funded by the DAO. Other vaults remain unaffected: DVV and EarnUSD are operating normally. The GGV sub-vault is currently experiencing negative yields due to a combination of recursive staking strategies and rising borrowing rates, but active adjustments are underway. Users’ previously submitted withdrawal requests will be processed at pre-incident valuations.
Vercel CEO Guillermo Rauch (@rauchg) announced that Vercel is conducting an in-depth investigation into the April 2026 security incident. The investigation revealed that the attackers initially breached Vercel’s systems via Context.ai’s account—a startup—but their activities extended far beyond this initial intrusion. Threat intelligence indicates that the attackers distributed malware to steal Vercel account credentials and API keys from other service providers, then used those keys to rapidly and extensively enumerate non-sensitive environment variables. To trace the root cause, Vercel has processed nearly 1 petabyte of network and API logs. Vercel is collaborating with industry partners—including Microsoft, AWS, and Wiz—to respond jointly and has proactively notified other potentially affected parties, urging them to rotate credentials and adopt security best practices.