Lazarus Group

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.

Slow Fog Cosine: Confirmed that the attacker of the CEX theft incident is the North Korean hacker group Lazarus Group, which has revealed its attack methods

ChainCatcher news, Slow Mist founder Yu Xian posted on social media, "Through forensic analysis and correlation tracking, we confirm that the attackers of the CEX theft incident are the North Korean hacker group Lazarus Group. This is a nation-state APT attack targeting cryptocurrency trading platforms. We have decided to share the relevant IOCs (Indicators of Compromise), which include some IPs of cloud service providers, proxies, etc. It is important to note that this disclosure does not specify which platform or platforms were involved, nor does it mention Bybit; if there are similarities, it is indeed not impossible."The attackers utilized pyyaml for RCE (Remote Code Execution), enabling the delivery of malicious code to control target computers and servers. This method bypassed most antivirus software. After synchronizing intelligence with partners, multiple similar malicious samples were obtained. The main goal of the attackers is to gain control over wallets by infiltrating the infrastructure of cryptocurrency trading platforms, thereby illegally transferring a large amount of cryptocurrency assets from the wallets.Slow Mist published a summary article revealing the attack methods of the Lazarus Group, and also analyzed their use of social engineering, vulnerability exploitation, privilege escalation, internal network penetration, and fund transfer tactics. At the same time, based on actual cases, they summarized defense recommendations against APT attacks, hoping to provide references for the industry and help more institutions enhance their security capabilities and reduce the impact of potential threats.

Zhao Changpeng: Proposing to suspend withdrawals is a prudent move, Bybit CEO makes the best decision based on the situation

ChainCatcher message, Binance founder Zhao Changpeng expressed detailed views on the recent hacking incident, "We have observed a pattern where hackers are able to steal large amounts of cryptocurrency from multi-signature 'cold storage' solutions. Exchanges like Bybit, Phemex, and WazirX have all encountered similar situations. In the recent Bybit case, hackers were able to make the front-end user interface display legitimate transactions, while the actual signatures pointed to another transaction. For other cases, based on limited information, it seems that similar methods were employed.What is even more concerning is that the affected exchanges used different multi-signature solution providers. The hacker organization Lazarus Group has demonstrated extremely advanced and widespread infiltration capabilities. It is still unclear whether the hackers successfully infiltrated multiple signing devices, the server side, or both were compromised.Some have questioned my previous suggestion to pause withdrawals as a standard security precaution (a tweet I posted while on the shuttle bus to the airport). My intention was to share a practical approach based on experience and observation, but there is no absolute right or wrong in this practice. My guiding principle has always been to lean towards the safer side. After any security incident, all operations should be paused to ensure we fully understand what happened, how the hackers infiltrated the system, which devices were compromised, and only after triple-checking for safety should we resume operations.Of course, pausing withdrawals may trigger more panic. In 2019, after a significant hacking incident of $40 million, we paused withdrawals for a week. When we resumed withdrawals (and deposits), the deposit volume actually exceeded the withdrawal volume. This does not mean that this method is better; each situation is different and requires judgment. I tweeted to share potentially effective practices, intending to express support in a timely manner. I believe Ben made the best decision based on the information available.Ben maintained transparent communication and a calm demeanor while handling this challenging situation. This stands in stark contrast to other CEOs lacking transparency, such as those from WazirX, FTX, etc.The cases mentioned here are all different. FTX is a case of fraud, and as for WazirX, I will refrain from commenting due to ongoing litigation.Most importantly, we should never take security for granted. It is essential to understand security knowledge so that you can choose the right tools for your needs. To this end, I will share an article I wrote a few years ago. Although some parts may be outdated, the basic concepts still apply. Stay safe (SAFU)!"

Analysis: The fund flow path of the Bybit hacker is ETH-BTC-fiat, and the process may have lasted for several years, gradually converting into selling pressure

ChainCatcher news, according to an analysis by Eric Wall, co-founder of Taproot Wizards, the Bybit theft incident has been largely confirmed to be the work of the North Korean hacker group Lazarus Group. According to Chainalysis's 2022 report, this organization typically follows a fixed pattern in handling stolen funds, a process that may take years. Data from 2022 shows that the organization still holds $55 million from the 2016 attack, indicating that they are not in a hurry to cash out quickly.The process for handling stolen funds is as follows:Step one: Convert all ERC20 tokens (including liquidity derivatives like stETH) into ETH;Step two: Exchange all obtained ETH for BTC;Step three: Gradually exchange BTC for RMB through Asian exchanges;Final use: It is claimed that these funds will be used to support North Korea's nuclear weapons and ballistic missile programs;Analysis indicates that Bybit is currently supplementing a gap of about $1.5 billion in ETH through borrowing, a strategy that may be based on the hope of recovering the stolen funds. However, given the confirmation that it is the work of the Lazarus Group, the likelihood of recovery is extremely low, and Bybit will have to purchase ETH to repay the loans. In the long term, Bybit's purchase of ETH may offset the actions of the Lazarus Group selling ETH for BTC, and the BTC acquired by the Lazarus Group will gradually convert into selling pressure over the next few years.
ChainCatcher Building the Web3 world with innovators