The recent $1.5 billion hack on Bybit revealed important lessons for the crypto world. This article explores how the attackers used the Safe Client to compromise systems.
Preliminary Conclusions About Safe App Compromise
Official reports revealed that a benign JavaScript file in the Safe app was replaced with malicious code on February 19 at 15:29:25 UTC. The attack specifically targeted Bybit’s Ethereum multisig wallet. The compromise occurred via a Safe developer machine, with a leaked account or API key.
Safe Official Statement
In its statement, Safe revealed that the attack was conducted by the Lazarus Group and affected a Bybit machine account, though Safe smart contracts remained unaffected. Additional security measures have been implemented to eliminate the attack vector. External security checks did not reveal vulnerabilities in Safe smart contracts or frontend source code.
Official FBI Report
The FBI reports that stolen assets were converted into BTC and other cryptocurrencies, likely to be laundered and turned into fiat via numerous addresses on various blockchains. Recommendations included blocking transactions with addresses connected to activity known as TraderTraitor by the FBI.
The attack has revealed numerous vulnerabilities in secure applications within the crypto space. Users and companies must remain vigilant and cautious about their systems’ security.
