vulnerabilities

The European Central Bank avoided a payment system "disaster," but exposed vulnerabilities in emergency response

ChainCatcher news, according to Jinshi reports, the European Central Bank's payment system experienced a major failure last Thursday, and the chaos that ensued during the 10 hours it took to identify and resolve the issue led to disruptions in welfare payments for over 15,000 Greeks, a large number of wages and pensions in Austria, and several financial transactions. The situation could have potentially worsened.If the situation had occurred or continued into the next day, i.e., at the end of February, it would have been a payday for many public sector employees, pensioners, and welfare recipients, and this chaos could have impacted millions of people and businesses, putting a strain on the banking system. According to officials from the Eurozone central bank, the core of the escalating turmoil was a hardware failure, but technicians took hours to identify the problem after initially misdiagnosing a database issue.Markus Ferber, a member of the European Parliament and a member of the committee overseeing the European Central Bank, stated, "A hardware failure is forgivable, but it is inexcusable if there is no backup that can be immediately activated when problems arise." An official from the European Central Bank indicated that the affected hardware did indeed have multiple backups, and the bank is analyzing why they did not activate.

Safe: The developer's machine was compromised, leading to the theft of Bybit; there are no vulnerabilities in the contract and frontend code

ChainCatcher news, Safe responded on platform X to Bybit's hacking forensic report, stating that the forensic review of the targeted attack by the Lazarus Group on Bybit concluded that the attack on Bybit Safe was executed through compromised Safe{Wallet} developer machines, leading to disguised malicious transactions.Lazarus is a government-backed North Korean hacking organization known for its complex social engineering attacks on developer credentials, sometimes combined with zero-day vulnerabilities. The forensic review by external security researchers did not indicate any vulnerabilities in the Safe smart contracts or the source code of the front end and services.Following the recent incident, the Safe{Wallet} team conducted a thorough investigation and has now phased the restoration of Safe{Wallet} on the Ethereum mainnet. The Safe{Wallet} team has completely rebuilt and reconfigured all infrastructure and rotated all credentials to ensure the complete elimination of the attack vector.After the final results of the investigation are released, the Safe{Wallet} team will publish a complete post-mortem analysis. The Safe{Wallet} front end is still operational and has implemented additional security measures. However, users need to be extra cautious and vigilant when signing transactions.
ChainCatcher Building the Web3 world with innovators