{"id":34355,"date":"2025-03-11T04:48:28","date_gmt":"2025-03-11T08:48:28","guid":{"rendered":"https:\/\/www.kaspersky.co.za\/blog\/?p=34355"},"modified":"2025-03-17T15:42:37","modified_gmt":"2025-03-17T13:42:37","slug":"bybit-hack-lessons-how-to-do-self-custody-properly","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.za\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/34355\/","title":{"rendered":"Lessons from the Bybit hack: how to store crypto safely"},"content":{"rendered":"<p>February 21 was a dark day for the crypto market as it suffered the largest heist in its history. Attackers made off with around $1.5 billion from Bybit, the world\u2019s second-largest crypto exchange, with experts citing it as the biggest theft \u2013 of anything \u2013 of all time. Although neither this loss nor the withdrawal of a further $5 billion by panicked investors were fatal for Bybit, the incident underscores the fundamental flaws in the modern crypto ecosystem, and serves up some valuable lessons for regular users.<\/p>\n<h2>How Bybit was robbed<\/h2>\n<p>Like all major crypto exchanges, Bybit secures stored cryptocurrency with multi-layered protection. Most funds are stored in <a href=\"https:\/\/www.kaspersky.com\/blog\/five-threats-hardware-crypto-wallets\/47971\/\" target=\"_blank\" rel=\"noopener nofollow\">cold wallets<\/a> disconnected from online systems. When current assets need topping up, the required sum is manually moved from the cold wallet to the hot one, and the operation is signed by several employees at once. For this, Bybit uses a multi-signature (multisig) solution from Safe{Wallet}, and each employee involved in the transaction signs it <a href=\"https:\/\/www.certik.com\/resources\/blog\/bybit-incident-technical-analysis\" target=\"_blank\" rel=\"nofollow noopener\">using a private Ledger hardware cryptokey<\/a>.<\/p>\n<p>The attackers studied the system in detail and, according to independent researchers, compromised a Safe{Wallet} developer machine. Presumably, malicious modifications were made to the code for displaying Safe{Wallet} web application pages. Having conducted their own investigation, the owners of Safe{Wallet} rejected the findings of the two independent information security companies, insisting that their infrastructure had not been hacked.<\/p>\n<p>So what happened? During a routine top-up of $7 million to a hot wallet, Bybit employees saw on their computer screens this exact amount and the recipient\u2019s address, which matched the hot wallet address. But other data got sent for signing instead! For regular transfers, the recipient\u2019s address can (and should!) be checked on the screen of the Ledger device. But when signing multisig transactions, this information isn\u2019t displayed \u2014 so Bybit employees essentially made a blind transfer.<\/p>\n<p>As a result, they inadvertently green-lighted a malicious smart contract that moved the entire contents of one of Bybit\u2019s cold wallets to several hundred fake wallets. As soon as the withdrawal from the Bybit wallet was complete, it appears that the code on the Safe{Wallet} website reverted to the harmless version. The attackers are currently busy \u201clayering\u201d the stolen Ethereum \u2014 transferring it piecemeal in an attempt to launder it.<\/p>\n<p>By the looks of it, Bybit and its clients were the victims of a targeted <a href=\"https:\/\/www.kaspersky.com\/blog\/supply-chain-attacks-what-are-they-and-how-to-manage-the-risk\/52852\/\" target=\"_blank\" rel=\"noopener nofollow\">supply-chain attack<\/a>.<\/p>\n<h2>The Bybit case is no one-off<\/h2>\n<p>The FBI has <a href=\"https:\/\/www.reuters.com\/technology\/cybersecurity\/fbi-says-north-korea-was-responsible-15-billion-bybit-hack-2025-02-27\/\" target=\"_blank\" rel=\"nofollow noopener\">officially named<\/a> a North Korean group codenamed TraderTraitor as the perpetrator. In information-security circles, this group is <a href=\"https:\/\/www.cisa.gov\/news-events\/cybersecurity-advisories\/aa22-108a\" target=\"_blank\" rel=\"nofollow noopener\">also known as Lazarus, APT38, or BlueNoroff<\/a>. Its trademark style is persistent, sophisticated and sustained attacks in the cryptocurrency sphere: hacking wallet developers, robbing crypto exchanges, stealing from ordinary users, and even <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-play-tanks-and-catch-backdoor\/52561\/\" target=\"_blank\" rel=\"noopener nofollow\">making fake play-to-earn games<\/a>.<\/p>\n<p>Before the Bybit raid, the group\u2019s record was the <a href=\"https:\/\/www.kaspersky.com\/blog\/sky-mavis-crypto-heist\/44981\/\" target=\"_blank\" rel=\"noopener nofollow\">theft of $540\u00a0million<\/a> from the Ronin Networks blockchain, created for the game <em>Axie Infinity<\/em>. In that 2022 attack, hackers infected the computer of one of the game\u2019s developers using a fake job offer in an infected PDF file. This social engineering technique <a href=\"https:\/\/securelist.com\/lazarus-new-malware\/115059\/\" target=\"_blank\" rel=\"noopener\">remains in the group\u2019s arsenal<\/a> to this day.<\/p>\n<p>In May 2024, the group pulled off a smash-and-grab of <a href=\"https:\/\/thenewscrypto.com\/fbi-links-308-million-dmm-bitcoin-hack-to-north-korean-hacker-group\/\" target=\"_blank\" rel=\"nofollow noopener\">over $300\u00a0million from Japanese crypto-exchange DMM Bitcoin<\/a>, which went bankrupt as a consequence. Before that, in 2020, more than $275 million was <a href=\"https:\/\/www.chainalysis.com\/blog\/lazarus-group-kucoin-exchange-hack\/\" target=\"_blank\" rel=\"nofollow noopener\">siphoned off the KuCoin crypto exchange<\/a>, with a \u201cleaked private key\u201d for a hot wallet cited as the reason.<\/p>\n<p>Lazarus has been honing its cryptocurrency theft tactics for over a decade now. In 2018, we wrote about a string of attacks on banks and crypto exchanges using a Trojanized cryptocurrency trading app as part of <a href=\"https:\/\/securelist.com\/operation-applejeus\/87553\/\" target=\"_blank\" rel=\"noopener\">Operation AppleJeus<\/a>. Experts at Elliptic <a href=\"https:\/\/www.elliptic.co\/blog\/bybit-hack-largest-in-history\" target=\"_blank\" rel=\"nofollow noopener\">estimate<\/a> that North-Korea-linked actors\u2019 total criminal earnings amount to around $6\u00a0billion.<\/p>\n<h2>What crypto investors should do<\/h2>\n<p>In the case of Bybit, clients were lucky: the exchange promptly serviced the wave of withdrawal requests that ensued, and promised to compensate losses from its own funds. Bybit remains in business, so clients don\u2019t need to take any particular action.<\/p>\n<p>But the hack demonstrates once again just how hard it is to secure funds flowing through blockchain systems, and how little can be done to cancel a transaction or refund money. Given the unprecedented scale of the attack, many have called for the Ethereum blockchain to be rolled back to its pre-hack state, but Ethereum developers <a href=\"https:\/\/cointelegraph.com\/news\/ethereum-rollback-debate-technically-intractable-eth-core-developer\" target=\"_blank\" rel=\"nofollow noopener\">consider this \u201ctechnically intractable\u201d<\/a>. Meanwhile, Bybit has <a href=\"https:\/\/markets.businessinsider.com\/news\/stocks\/bybit-launches-recovery-bounty-program-with-rewards-up-to-10-of-stolen-funds-1034394717\" target=\"_blank\" rel=\"nofollow noopener\">announced a bounty program<\/a> for crypto exchanges and ethical researchers to the tune of 10% of any funds recovered, but so far only $43\u00a0million has materialized.<\/p>\n<p>This has caused some <a href=\"https:\/\/cointelegraph.com\/news\/bybit-hack-security-execs-weigh-in\" target=\"_blank\" rel=\"nofollow noopener\">crypto industry experts<\/a> to speculate that the main fallout from the hack will be a rise in <a href=\"https:\/\/x.com\/StaniKulechov\/status\/1892974833828331702\" target=\"_blank\" rel=\"nofollow noopener\">self-custody of crypto assets<\/a>.<\/p>\n<p><strong>Self-custody<\/strong> shifts the responsibility for secure storage from the shoulders of specialists to your own. Therefore, only go down this route if you have total confidence in your abilities to master all security measures and follow them rigidly day by day. Note that regular users without cryptowallet millions are unlikely to face a sophisticated attack targeted specifically at them, while generic mass attacks are easier to deflect.<\/p>\n<p>So, what do you need for secure self-custody of cryptocurrency?<\/p>\n<ul>\n<li><strong>Buy a hardware wallet with a screen.<\/strong> This is the most effective way to protect crypto assets. Do a little research first, and be sure to buy a wallet from a reputable vendor \u2014 and directly: never second-hand or from a marketplace. Otherwise, you might get a <a href=\"https:\/\/www.kaspersky.com\/blog\/fake-trezor-hardware-crypto-wallet\/48155\/\" target=\"_blank\" rel=\"noopener nofollow\">pre-hacked wallet<\/a> that swallows up all your funds. When using a wallet to sign transfers, always check the recipient\u2019s address on both the computer screen and the wallet screen to rule out its substitution by a <a href=\"https:\/\/www.kaspersky.com\/blog\/what-is-a-crypto-wallet-drainer\/50490\/\" target=\"_blank\" rel=\"noopener nofollow\">malicious smart contract<\/a> or a <a href=\"https:\/\/securelist.com\/copy-paste-heist-clipboard-injector-targeting-cryptowallets\/109186\/\" target=\"_blank\" rel=\"noopener\">clipper Trojan<\/a> that replaces cryptowallet addresses in the clipboard.<\/li>\n<li><strong>Never store wallet seed phrases in electronic form.<\/strong> Forget about using files on your computer and photos in your gallery for that\u00a0\u2014 modern Trojans have <a href=\"https:\/\/www.kaspersky.com\/blog\/ios-android-ocr-stealer-sparkcat\/52980\/\" target=\"_blank\" rel=\"noopener nofollow\">learned to infiltrate Google Play and the App Store and recognize data in photos<\/a> stored on your smartphone. Only paper records (or metal engravings, if you prefer) kept inside a safe or in another physically secure place, protected from both unauthorized access and natural disasters, will do. You might consider multiple storage locations, as well as splitting your seed phrase into parts.<\/li>\n<li><strong>Don\u2019t keep all your <span style=\"text-decoration: line-through;\">eggs<\/span> coins in one basket.<\/strong> For holders of large amounts or different types of crypto assets, it makes sense to use multiple wallets. Small amounts for transactional needs can be stored on a crypto exchange, while the bulk can be divided among several hardware cryptowallets.<\/li>\n<li><strong>Use a dedicated computer.<\/strong> If possible, dedicate a computer for cryptocurrency transactions. Physically restrict access to it (e.g., put it in a safe, a locked cupboard or locked room), use disk encryption and password login, and have a separate account with its own passwords (i.e., different to those on your main computer). Install <a href=\"https:\/\/www.kaspersky.co.za\/premium?icid=en-za_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">reliable protection<\/a>\u00a0and enable maximum security settings on your \u201ccrypto-computer\u201d. Connect it to the internet only for transactions, and use it solely for operations with wallets. Playing games, reading crypto news, and chatting with friends are for another device.<\/li>\n<li>If dedicating a computer is impractical or uneconomical, <strong>maintain strict digital hygiene on your main computer<\/strong>. Set up a separate account with low privileges (non-administrator) for crypto operations, and another account \u2014 also non-administrator \u2014 for work, chat and games. There\u2019s no need to work in administrator mode at all, except to update the system software or significantly reconfigure the computer. Sign in to your dedicated \u201ccrypto account\u201d only for operations with wallets, and sign out immediately afterward. Don\u2019t give outsiders access to the computer, and don\u2019t share admin passwords with anyone.<\/li>\n<li><strong>Take care when choosing cryptowallet software.<\/strong> Carefully study the software\u2019s description, make sure that the application has been on the market for a long time, and check that you\u2019re downloading it from the official website, and that the digital signature of the distribution corresponds to the website and the name of the vendor. Perform a deep scan of your computer with an <a href=\"https:\/\/www.kaspersky.co.za\/premium?icid=en-za_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">up-to-date security solution<\/a>\u00a0before installing and running cryptowallet software.<\/li>\n<li><strong>Be careful with updates.<\/strong> While we usually recommend updating all software right away, in the case of cryptocurrency applications, it\u2019s worth adjusting this policy a little. After the release of a new version, wait about a week and read the reviews before installing it. This will give the community time to catch any bugs or Trojans that may have sneaked into the update.<\/li>\n<li><strong>Follow the enhanced computer security measures<\/strong> described in our post <a href=\"https:\/\/www.kaspersky.com\/blog\/4-key-steps-to-protect-cryptocurrency-properly\/47811\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Protecting crypto investments: four key steps to safety<\/strong><\/a>, which include installing a powerful security solution, <a href=\"https:\/\/www.kaspersky.co.za\/premium?icid=en-za_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">such as Kaspersky Premium<\/a>, on your computer and smartphone, regularly updating your operating system and browsers, and using strong, unique passwords.<\/li>\n<li><strong>Expect phishing.<\/strong> Cryptocurrency fraud can be both multifaceted and sophisticated, so any unexpected messages by email, messenger app and the like should be seen as the start of a scam. Keep on top of all the latest crypto scams by following <a href=\"https:\/\/www.kaspersky.com\/blog\/tag\/cryptocurrencies\/\" target=\"_blank\" rel=\"noopener nofollow\">our blog<\/a> or <a href=\"https:\/\/t.me\/kasperskygl\" target=\"_blank\" rel=\"nofollow noopener\">Telegram channel<\/a>, as well as other reputable cybersecurity sources.<\/li>\n<\/ul>\n<blockquote><p>Read more about crypto scams and ways to protect yourself in our dedicated posts:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/top-eight-crypto-scams-2023\/48489\/\" target=\"_blank\" rel=\"noopener nofollow\">Eight of the most daring crypto thefts in history<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/top-5-cryptocurrency-heists\/34151\/\" target=\"_blank\" rel=\"noopener nofollow\">The top-5 biggest cryptocurrency heists ever<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/fake-trezor-hardware-crypto-wallet\/48155\/\" target=\"_blank\" rel=\"noopener nofollow\">Case study: fake hardware cryptowallet<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/pig-butchering-crypto-investment-scam\/50764\/\" target=\"_blank\" rel=\"noopener nofollow\">Pig butchering: large-scale cryptocurrency fraud<\/a><\/li>\n<li>and other <a href=\"https:\/\/www.kaspersky.com\/blog\/tag\/cryptocurrencies\/\" target=\"_blank\" rel=\"noopener nofollow\">articles about cryptocurrency<\/a>.<\/li>\n<\/ul>\n<\/blockquote>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-crypto-generic\">\n","protected":false},"excerpt":{"rendered":"<p>Takeaways for regular crypto holders from the biggest crypto heist in history. <\/p>\n","protected":false},"author":2722,"featured_media":34356,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2670],"tags":[374,1035,2646,2872,2697,187,76,726,2889,422,131],"class_list":{"0":"post-34355","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-bitcoin","9":"tag-blockchain","10":"tag-cryptocurrencies","11":"tag-cryptowallet","12":"tag-ethereum","13":"tag-passwords","14":"tag-phishing","15":"tag-scam","16":"tag-supply-chain","17":"tag-threats","18":"tag-tips"},"hreflang":[{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/34355\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/28661\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/23900\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/12321\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/28778\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/27995\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/30815\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/29507\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/39186\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/13214\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/53155\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/22637\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/23601\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/32010\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/bybit-hack-lessons-how-to-do-self-custody-properly\/28908\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/bybit-hack-lessons-how-to-do-self-custody-properly\/34728\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.za\/blog\/tag\/scam\/","name":"scam"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/34355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/users\/2722"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/comments?post=34355"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/34355\/revisions"}],"predecessor-version":[{"id":34367,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/34355\/revisions\/34367"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/media\/34356"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/media?parent=34355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/categories?post=34355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/tags?post=34355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}