{"id":11903,"date":"2023-12-11T16:09:05","date_gmt":"2023-12-11T13:09:05","guid":{"rendered":"https:\/\/www.kaspersky.com.tr\/blog\/?p=11903"},"modified":"2023-12-11T16:13:41","modified_gmt":"2023-12-11T13:13:41","slug":"vulnerability-in-hot-cryptowallets-from-2011-2015","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.tr\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/11903\/","title":{"rendered":"Randstorm: 2010&#8217;lardan kalma savunmas\u0131z kripto c\u00fczdanlar\u0131"},"content":{"rendered":"<p>Ara\u015ft\u0131rmac\u0131lar BitcoinJS k\u00fct\u00fcphanesinde, on y\u0131l \u00f6nce \u00e7evrimi\u00e7i olarak olu\u015fturulan Bitcoin c\u00fczdanlar\u0131n\u0131 ele ge\u00e7irilmeye a\u00e7\u0131k hale getirebilecek \u00e7e\u015fitli g\u00fcvenlik a\u00e7\u0131klar\u0131 ke\u015ffetti. Temel sorun, bu kripto c\u00fczdanlar\u0131n\u0131n \u00f6zel anahtarlar\u0131n\u0131n k\u00fct\u00fcphane geli\u015ftiricilerinin bekledi\u011finden \u00e7ok daha y\u00fcksek bir \u00f6ng\u00f6r\u00fclebilirlikle \u00fcretilmi\u015f olmas\u0131yd\u0131.<\/p>\n<h2>Randstorm g\u00fcvenlik a\u00e7\u0131klar\u0131 ve sonu\u00e7lar\u0131<\/h2>\n<p>Meseleyi en ba\u015ftan ele alal\u0131m. Kripto c\u00fczdan eri\u015fimi kurtarma konusunda uzmanla\u015fm\u0131\u015f bir \u015firket olan Unciphered\u2019deki ara\u015ft\u0131rmac\u0131lar, bir\u00e7ok \u00e7evrimi\u00e7i kripto para birimi platformu taraf\u0131ndan kullan\u0131lan BitcoinJS JavaScript k\u00fct\u00fcphanesinde bir dizi g\u00fcvenlik a\u00e7\u0131\u011f\u0131 <a href=\"https:\/\/www.unciphered.com\/blog\/randstorm-you-cant-patch-a-house-of-cards\" target=\"_blank\" rel=\"nofollow noopener\">ke\u015ffetti ve a\u00e7\u0131klad\u0131<\/a>. Bu hizmetler aras\u0131nda \u00e7ok pop\u00fcler olanlar ve \u00f6zellikle de art\u0131k Blockchain.com olarak bilinen Blockchain.info da bulunuyor. Bu g\u00fcvenlik a\u00e7\u0131\u011f\u0131 k\u00fcmesine ara\u015ft\u0131rmac\u0131lar taraf\u0131ndan Randstorm ad\u0131 verildi.<\/p>\n<p>BitcoinJS k\u00fct\u00fcphanesindeki g\u00fcvenlik a\u00e7\u0131klar\u0131 2014 y\u0131l\u0131nda giderilmi\u015f olsa da, sorun bu k\u00fct\u00fcphanenin kullan\u0131m\u0131n\u0131n sonu\u00e7lar\u0131n\u0131 da kaps\u0131yor: 2010\u2019lar\u0131n ba\u015f\u0131nda BitcoinJS ile olu\u015fturulan t\u00fcm kripto c\u00fczdanlar\u0131 g\u00fcvensiz olabilir \u00e7\u00fcnk\u00fc \u00f6zel anahtarlar\u0131n\u0131 bulmak, altta yatan Bitcoin kriptografisinin varsayd\u0131\u011f\u0131ndan \u00e7ok daha kolay.<\/p>\n<p>Ara\u015ft\u0131rmac\u0131lar, toplamda yakla\u015f\u0131k 1,4 milyon BTC\u2019ye tekab\u00fcl eden birka\u00e7 milyon c\u00fczdan\u0131n Randstorm nedeniyle potansiyel olarak risk alt\u0131nda oldu\u011funu tahmin ediyor. Ara\u015ft\u0131rmac\u0131lara g\u00f6re, <em>potansiyel<\/em> olarak savunmas\u0131z c\u00fczdanlar\u0131n %3 ila %5\u2019i ger\u00e7ek sald\u0131r\u0131lara kar\u015f\u0131 <em>savunmas\u0131z durumda<\/em>. Yay\u0131n\u0131n\u00a0 yap\u0131ld\u0131\u011f\u0131 tarihte yakla\u015f\u0131k 36.500 $ olan Bitcoin kuruna g\u00f6re bu, Randstorm\u2019dan ba\u015far\u0131yla yararlanabilen sald\u0131rganlar i\u00e7in toplam 1,5 ila 2,5 milyar $\u2019l\u0131k bir ganimet anlam\u0131na geliyor.<\/p>\n<p>Ara\u015ft\u0131rmac\u0131lar, Randstorm g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131n ger\u00e7ekten de kripto c\u00fczdanlar\u0131na y\u00f6nelik ger\u00e7ek d\u00fcnya sald\u0131r\u0131lar\u0131 i\u00e7in kullan\u0131labilece\u011fini iddia ediyor. Dahas\u0131, Mart 2012\u2019den \u00f6nce Blockchain.info\u2019da olu\u015fturulan birka\u00e7 kripto c\u00fczdan\u0131na eri\u015fimi yeniden sa\u011flamak i\u00e7in bu g\u00fcvenlik a\u00e7\u0131klar\u0131ndan ba\u015far\u0131yla yararland\u0131lar. Etik nedenlerden \u00f6t\u00fcr\u00fc, on binlerce kripto c\u00fczdan\u0131n\u0131 do\u011frudan h\u0131rs\u0131zl\u0131k riskine maruz b\u0131rakaca\u011f\u0131ndan sald\u0131r\u0131 i\u00e7in kavram kan\u0131tlama yay\u0131nlamad\u0131lar.<\/p>\n<p>Ara\u015ft\u0131rmac\u0131lar, BitcoinJS k\u00fct\u00fcphanesinin g\u00fcvenlik a\u00e7\u0131\u011f\u0131 bulunan s\u00fcr\u00fcmlerini kulland\u0131\u011f\u0131 bilinen \u00e7evrimi\u00e7i kripto para hizmetleriyle \u00e7oktan ileti\u015fime ge\u00e7ti. Bu hizmetler de Randstorm\u2019dan potansiyel olarak etkilenebilecek m\u00fc\u015fterileri bilgilendirdi.<\/p>\n<h2>Randstorm g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131n do\u011fas\u0131<\/h2>\n<p>\u015eimdi bu g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131n ger\u00e7ekte nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131na daha ayr\u0131nt\u0131l\u0131 olarak bakal\u0131m. Bitcoin c\u00fczdan g\u00fcvenli\u011finin temelinde \u00f6zel anahtar vard\u0131r. Her modern kriptografik sistem gibi Bitcoin de bu anahtar\u0131n gizli ve k\u0131r\u0131lamaz olmas\u0131na dayan\u0131r. Yine, her modern kriptografik sistemde oldu\u011fu gibi, bu da \u00e7ok uzun rastgele say\u0131lar\u0131n kullan\u0131lmas\u0131n\u0131 gerektirir.<\/p>\n<p>Ve \u00f6zel anahtar taraf\u0131ndan korunan herhangi bir verinin g\u00fcvenli\u011fi i\u00e7in, bu say\u0131lar\u0131n olabildi\u011fince rastgele olmas\u0131 gerekir. Anahtar olarak kullan\u0131lan say\u0131 y\u00fcksek tahmin edilebilirli\u011fe sahip olursa, anahtar olu\u015fturma prosed\u00fcr\u00fc hakk\u0131nda bilgi sahibi olan bir sald\u0131rgan\u0131n bu say\u0131y\u0131 deneme yan\u0131lma y\u00f6ntemiyle elde etmesi daha kolay ve h\u0131zl\u0131 olur.<\/p>\n<p>Rastgele bir say\u0131 \u00fcretmenin <em>asl\u0131nda<\/em> <a href=\"https:\/\/engineering.mit.edu\/engage\/ask-an-engineer\/can-a-computer-generate-a-truly-random-number\/\" target=\"_blank\" rel=\"nofollow noopener\">o kadar da kolay<\/a> olmad\u0131\u011f\u0131n\u0131 unutmay\u0131n. Ayr\u0131ca bilgisayarlar do\u011falar\u0131 gere\u011fi bu g\u00f6rev i\u00e7in son derece elveri\u015fsizdir \u00e7\u00fcnk\u00fc \u00e7ok \u00f6ng\u00f6r\u00fclebilirdirler. Bu nedenle, genellikle sahip oldu\u011fumuz \u015fey <em>s\u00f6zde rastgele<\/em> say\u0131lard\u0131r ve \u00fcretimin <em>entropisini<\/em> (kriptograf dilinde \u00f6ng\u00f6r\u00fclemezlik \u00f6l\u00e7\u00fcs\u00fc) art\u0131rmak i\u00e7in \u00f6zel i\u015flevlere g\u00fcveniriz.<\/p>\n<p>\u015eimdi BitcoinJS k\u00fct\u00fcphanesine geri d\u00f6nelim. \u201cY\u00fcksek kaliteli\u201d s\u00f6zde rastgele say\u0131lar elde etmek i\u00e7in bu k\u00fct\u00fcphane JSBN (JavaScript Big Number) adl\u0131 ba\u015fka bir JavaScript k\u00fct\u00fcphanesini, \u00f6zellikle de <em>SecureRandom<\/em> i\u015flevini kullan\u0131yor. Ad\u0131ndan da anla\u015f\u0131laca\u011f\u0131 gibi, bu i\u015flev kriptografide kullan\u0131lmaya uygun s\u00f6zde rastgele say\u0131lar \u00fcretmek i\u00e7in tasarlanm\u0131\u015ft\u0131r. Entropilerini art\u0131rmak i\u00e7in <em>SecureRandom<\/em>, <em>window.crypto.random<\/em> taray\u0131c\u0131 i\u015flevine g\u00fcvenir.<\/p>\n<p>Sorun da zaten burada yat\u0131yor: <em>window.crypto.random<\/em> i\u015flevi Netscape Navigator 4.x taray\u0131c\u0131 ailesinde mevcut olsa da, web hizmetleri BitcoinJS k\u00fct\u00fcphanesini aktif olarak kullanmaya ba\u015flad\u0131\u011f\u0131nda bu taray\u0131c\u0131lar \u00e7oktan kullan\u0131lmaz hale gelmi\u015fti bile. Ve o g\u00fcnlerin pop\u00fcler taray\u0131c\u0131lar\u0131nda )(Internet Explorer, Google Chrome, Mozilla Firefox ve Apple Safari)<em>window.crypto.random <\/em>i\u015flevi basit\u00e7e uygulanm\u0131yordu.<\/p>\n<p>Ne yaz\u0131k ki, JSBN k\u00fct\u00fcphanesinin geli\u015ftiricileri herhangi bir kontrol veya ilgili hata mesaj\u0131 i\u00e7in haz\u0131rl\u0131k yapmam\u0131\u015ft\u0131. Bunun neticesinde, <em>SecureRandom<\/em> i\u015flevi entropi art\u0131rma ad\u0131m\u0131n\u0131 sessizce ge\u00e7erek \u00f6zel anahtar olu\u015fturma g\u00f6revini standart s\u00f6zde rastgele say\u0131 \u00fcreteci <em>Math.random<\/em>\u2018a devretti.<\/p>\n<p>Bu durumun kendisi zaten \u00e7ok vahimdir \u00e7\u00fcnk\u00fc <em>Math.random<\/em> kriptografik ama\u00e7lar i\u00e7in uygun <a href=\"https:\/\/security.stackexchange.com\/questions\/181580\/why-is-math-random-not-designed-to-be-cryptographically-secure\" target=\"_blank\" rel=\"nofollow noopener\">de\u011fildir<\/a>. Ancak <a href=\"https:\/\/jandemooij.nl\/blog\/math-random-and-32-bit-precision\/\" target=\"_blank\" rel=\"nofollow noopener\">ba\u015fta Google Chrome<\/a> olmak \u00fczere 2011-2015 y\u0131llar\u0131n\u0131n pop\u00fcler taray\u0131c\u0131lar\u0131ndaki <em>Math.random<\/em> uygulamas\u0131n\u0131n, olmas\u0131 gerekenden daha az rastgele say\u0131 elde edilmesine neden olan hatalar i\u00e7ermesi durumu daha da karma\u015f\u0131k hale getirmektedir.<\/p>\n<p>B\u00f6ylece, BitcoinJS k\u00fct\u00fcphanesi yukar\u0131da bahsedilen t\u00fcm sorunlar\u0131 JSBN\u2019den devralm\u0131\u015f oldu. Sonu\u00e7 olarak, kripto c\u00fczdanlar\u0131 i\u00e7in \u00f6zel anahtarlar \u00fcretmek i\u00e7in kullanan platformlar, SecureRandom i\u015flevi sayesinde k\u00fct\u00fcphane geli\u015ftiricilerinin bekledi\u011finden \u00e7ok daha az rastgele say\u0131 elde etti. Ve bu anahtarlar b\u00fcy\u00fck bir \u00f6ng\u00f6r\u00fclebilirlikle \u00fcretildi\u011finden, deneme yan\u0131lma ile k\u0131r\u0131lmalar\u0131 \u00e7ok daha kolayd\u0131r ve savunmas\u0131z kripto c\u00fczdanlar\u0131n\u0131n ele ge\u00e7irilmesine olanak tan\u0131r.<\/p>\n<p>Yukar\u0131da belirtildi\u011fi gibi, bu teorik bir tehlike de\u011fil, olduk\u00e7a pratik bir tehlikedir. Unciphered ekibi, Blockchain.info\u2019da olu\u015fturulan birka\u00e7 eski kripto c\u00fczdan\u0131na eri\u015fimi geri almak (ba\u015fka bir deyi\u015fle, etik olarak hacklemek) i\u00e7in bu g\u00fcvenlik a\u00e7\u0131klar\u0131ndan yararlanmay\u0131 ba\u015fard\u0131.<\/p>\n<h2>Randstorm riski alt\u0131nda olanlar<\/h2>\n<p>BitcoinJS, 2011\u2019deki tan\u0131t\u0131m\u0131ndan 2014\u2019e kadar savunmas\u0131z JSBN k\u00fct\u00fcphanesini kullanm\u0131\u015ft\u0131r. Bununla birlikte, baz\u0131 kripto para projelerinin bir s\u00fcredir k\u00fct\u00fcphanenin en son s\u00fcr\u00fcm\u00fcnden daha d\u00fc\u015f\u00fck s\u00fcr\u00fcmlerini kullan\u0131yor olabilece\u011fini de unutmay\u0131n. Pop\u00fcler taray\u0131c\u0131larda Math.random\u2019u etkileyen hatalara gelince, 2016 y\u0131l\u0131na kadar s\u00f6zde rastgele say\u0131 \u00fcretme algoritmalar\u0131 de\u011fi\u015ftirilerek d\u00fczeltildi. Bunlar bir araya getirildi\u011finde, potansiyel olarak savunmas\u0131z kripto c\u00fczdanlar\u0131n\u0131n olu\u015fturuldu\u011fu zaman diliminin yakla\u015f\u0131k 2011-2015 oldu\u011fu ortaya \u00e7\u0131k\u0131yor.<\/p>\n<p>Ara\u015ft\u0131rmac\u0131lar, BitcoinJS\u2019nin 2010\u2019lar\u0131n ba\u015f\u0131nda \u00e7ok pop\u00fcler oldu\u011funu, bu nedenle savunmas\u0131z bir s\u00fcr\u00fcm\u00fc kullanm\u0131\u015f olabilecek hizmetlerin tam bir listesini derlemenin zor oldu\u011funu vurguluyor. Haz\u0131rlad\u0131klar\u0131 raporda, risk alt\u0131nda oldu\u011funu tespit ettikleri platformlar\u0131n bir listesi yer al\u0131yor:<\/p>\n<ul>\n<li><strong>BitAddress<\/strong> \u2013 hala \u00e7al\u0131\u015f\u0131r durumda.<\/li>\n<li><strong>BitCore<\/strong> (BitPay) \u2013 hala \u00e7al\u0131\u015f\u0131r durumda.<\/li>\n<li><strong>Bitgo<\/strong> \u2013 hala \u00e7al\u0131\u015f\u0131r durumda.<\/li>\n<li><strong>info<\/strong> \u2013 Blockchain.com olarak hala \u00e7al\u0131\u015f\u0131r durumda.<\/li>\n<li><strong>Blocktrail<\/strong> \u2014 <code> https:\/\/btc.com <\/code> veya <code> https:\/\/blockchair.com <\/code> adresine y\u00f6nlendiriyor.<\/li>\n<li><strong>BrainWallet<\/strong> \u2013 kapand\u0131<strong>.<\/strong><\/li>\n<li><strong>CoinKite<\/strong> \u2013 art\u0131k donan\u0131m c\u00fczdanlar\u0131 sat\u0131yor.<\/li>\n<li><strong>CoinPunk<\/strong> \u2013 kapand\u0131.<\/li>\n<li><strong>Dark Wallet<\/strong> \u2014 <code> https:\/\/crypto-engine.org <\/code> adresine y\u00f6nlendiriyor.<\/li>\n<li><strong>DecentralBank<\/strong> \u2013 kapand\u0131<strong>.<\/strong><\/li>\n<li><strong>info<\/strong> (Block.io) \u2013 hala \u00e7al\u0131\u015f\u0131r durumda.<\/li>\n<li><strong>EI8HT<\/strong> \u2013 kapand\u0131.<\/li>\n<li><strong>GreenAddress<\/strong> \u2014 <code> https:\/\/blockstream.com\/green\/ <\/code> adresine y\u00f6nlendiriyor.<\/li>\n<li><strong>QuickCon<\/strong> kapand\u0131.<\/li>\n<li><strong>Robocoin<\/strong> \u2013 kapand\u0131<strong>.<\/strong><\/li>\n<li><strong>Skyhook ATM<\/strong> \u2014 <code> https:\/\/yuan-pay-group.net <\/code> adresine y\u00f6nlendiriyor.<\/li>\n<\/ul>\n<p>Bitcoin c\u00fczdanlar\u0131n\u0131n yan\u0131 s\u0131ra Litecoin, Zcash ve Dogecoin c\u00fczdanlar\u0131 da risk alt\u0131nda olabilir, \u00e7\u00fcnk\u00fc bu kripto para birimleri i\u00e7in de BitcoinJS tabanl\u0131 k\u00fct\u00fcphaneler bulunmaktad\u0131r. Bu k\u00fct\u00fcphanelerin ilgili kripto c\u00fczdanlar\u0131 i\u00e7in \u00f6zel anahtarlar \u00fcretmek amac\u0131yla kullan\u0131labilece\u011fini varsaymak do\u011fal g\u00f6r\u00fcn\u00fcyor.<\/p>\n<p>Unciphered raporu Randstorm ile ilgili bir dizi ba\u015fka karma\u015f\u0131kl\u0131\u011f\u0131 da a\u00e7\u0131kl\u0131yor. Ancak temelde durum, 2011-2015 y\u0131llar\u0131 aras\u0131nda savunmas\u0131z k\u00fct\u00fcphane kullan\u0131larak olu\u015fturulan c\u00fczdanlar\u0131n, belirli ko\u015fullara ba\u011fl\u0131 olarak de\u011fi\u015fen derecelerde savunmas\u0131z olabilece\u011fi.<\/p>\n<h2>Randstorm\u2019a kar\u015f\u0131 nas\u0131l korunulur?<\/h2>\n<p>Ara\u015ft\u0131rmac\u0131lar\u0131n da hakl\u0131 olarak belirtti\u011fi gibi, yaz\u0131l\u0131mdaki g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131n d\u00fczeltilmesi yeterli olmayacakt\u0131r: c\u00fczdan sahiplerinin \u00f6zel anahtarlar\u0131n\u0131n \u201cyamalanmas\u0131\u201d ve g\u00fcvenli anahtarlarla de\u011fi\u015ftirilmesi m\u00fcmk\u00fcn de\u011fildir. Bu nedenle, hatalar uzun s\u00fcredir d\u00fczeltilmi\u015f olmas\u0131na ra\u011fmen, yukar\u0131da tart\u0131\u015f\u0131lan hatalar BitcoinJS k\u00fct\u00fcphanesinin etkilendi\u011fi d\u00f6nemde olu\u015fturulan kripto c\u00fczdanlar\u0131 i\u00e7in sorun olmaya devam ediyor. Bu, savunmas\u0131z c\u00fczdan sahiplerinin kendi ba\u015flar\u0131na koruyucu \u00f6nlemler almas\u0131 gerekti\u011fi anlam\u0131na geliyor.<\/p>\n<p>Savunmas\u0131z k\u00fct\u00fcphaneyi kullanan kripto para platformlar\u0131n\u0131n tam bir listesini \u00e7\u0131karmak zor oldu\u011fundan, g\u00fcvenli\u011fi tercih etmek ve 2011-2015 y\u0131llar\u0131 aras\u0131nda <em>\u00e7evrimi\u00e7i<\/em> olarak olu\u015fturulan herhangi bir kripto c\u00fczdan\u0131n\u0131 potansiyel olarak g\u00fcvensiz olarak kabul etmek daha iyidir (\u00f6yle olmad\u0131\u011f\u0131ndan eminseniz ba\u015fka). Ve do\u011fal olarak, c\u00fczdan ne kadar dolu olursa, su\u00e7lular i\u00e7in o kadar cazip olur.<\/p>\n<p>Sorunun bariz (ve tek) \u00e7\u00f6z\u00fcm\u00fc, yeni kripto c\u00fczdanlar\u0131 olu\u015fturmak ve potansiyel olarak savunmas\u0131z c\u00fczdanlardaki t\u00fcm fonlar\u0131 bunlara ta\u015f\u0131makt\u0131r.<\/p>\n<p>Ve bunu yaparken bu sefer son derece dikkatli ilerlemek mant\u0131kl\u0131d\u0131r. Kripto korumas\u0131 \u00e7ok ad\u0131ml\u0131 bir s\u00fcre\u00e7tir, bu nedenle ba\u011flant\u0131lardan eri\u015filebilen bir\u00e7ok ek bilgi ile birlikte sizin i\u00e7in kapsaml\u0131 bir kontrol listesi haz\u0131rlad\u0131k:<\/p>\n<ol>\n<li><a href=\"https:\/\/www.kaspersky.com.tr\/blog\/4-key-steps-to-protect-cryptocurrency-properly\/11394\/\" target=\"_blank\" rel=\"noopener\">Ana kripto tehditlerini ve koruma y\u00f6ntemlerini ayr\u0131nt\u0131l\u0131 olarak<\/a> \u00f6\u011frenin.<\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/top-5-cryptocurrency-heists\/34151\/\" target=\"_blank\" rel=\"noopener nofollow\">S\u0131cak ve so\u011fuk kripto c\u00fczdanlar\u0131 aras\u0131ndaki farklar\u0131<\/a> ve <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/top-eight-crypto-scams-2023\/11549\/\" target=\"_blank\" rel=\"noopener\">bunlara sald\u0131rman\u0131n en yayg\u0131n yollar\u0131n\u0131<\/a> anlay\u0131n.<\/li>\n<li>Temel kripto varl\u0131klar\u0131n\u0131n uzun s\u00fcreli depolanmas\u0131 i\u00e7in bir donan\u0131m (so\u011fuk) c\u00fczdan ve g\u00fcnl\u00fck i\u015flemler i\u00e7in minimum fon i\u00e7eri\u011fine sahip bir s\u0131cak c\u00fczdan kullan\u0131n.<\/li>\n<li>T\u00fcm fonlar\u0131 eski c\u00fczdandan yenisine aktarmadan \u00f6nce, t\u00fcm cihazlar\u0131n\u0131z\u0131 <a href=\"https:\/\/www.kaspersky.com.tr\/premium?icid=tr_bb2023-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">g\u00fcvenilir koruma<\/a> ile donat\u0131n. Bu, ak\u0131ll\u0131 telefonunuzu veya bilgisayar\u0131n\u0131z\u0131 <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/doublefinger-crypto-stealer-2\/11542\/\" target=\"_blank\" rel=\"noopener\">parolalar\u0131 ve \u00f6zel anahtarlar\u0131 \u00e7almak isteyen Truva<\/a> atlar\u0131na veya <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/doublefinger-crypto-stealer-2\/11542\/\" target=\"_blank\" rel=\"noopener\">panodaki kripto c\u00fczdan adreslerini de\u011fi\u015ftiren k\u0131rp\u0131c\u0131lara<\/a> kar\u015f\u0131 koruman\u0131n yan\u0131 s\u0131ra bilgisayar\u0131n\u0131z\u0131 <a href=\"https:\/\/www.kaspersky.com\/blog\/malicious-cryptominers-2022\/46186\/\" target=\"_blank\" rel=\"noopener nofollow\">k\u00f6t\u00fc niyetli kripto madencilerinden<\/a> ve yetkisiz uzaktan eri\u015fimden de koruyacakt\u0131r.<\/li>\n<li>Tohum c\u00fcmlenizin foto\u011fraf\u0131n\u0131 veya ekran g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc asla ak\u0131ll\u0131 telefonunuzda saklamay\u0131n, tohum c\u00fcmlenizi asla \u00fccretsiz bulut hizmetlerine y\u00fcklemeyin, asla mesajla\u015fma programlar\u0131 veya e-posta yoluyla g\u00f6ndermeyin ve kay\u0131p bir \u00f6zel anahtar\u0131 kurtarma i\u015flemleri hari\u00e7 olmak \u00fczere <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/cryptocurrency-giveaway-scam\/10691\/\" target=\"_blank\" rel=\"noopener\">hi\u00e7bir yere girmeyin<\/a>.<\/li>\n<li>Gerekti\u011finde ula\u015fmak i\u00e7in \u00f6zel anahtar\u0131n\u0131z\u0131 ve tohum c\u00fcmlenizi g\u00fcvenli bir \u015fekilde saklay\u0131n. Bu, depolanan t\u00fcm verileri AES-256 kullanarak \u015fifreleyen <a href=\"https:\/\/www.kaspersky.com.tr\/premium?icid=tr_bb2023-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">Kaspersky Premium<\/a> adresindeki <em>Kimlik Koruma C\u00fczdan\u0131<\/em> kullan\u0131larak yap\u0131labilir. Bunun i\u00e7in parola beyniniz d\u0131\u015f\u0131nda hi\u00e7bir yerde saklanmaz (tabii monit\u00f6r\u00fcn\u00fcze ili\u015ftirilmi\u015f bir yap\u0131\u015fkan nota yazmad\u0131\u011f\u0131n\u0131z\u0131 da varsay\u0131yoruz) ve kurtar\u0131lamaz, bu nedenle ki\u015fisel belgelerinize eri\u015fimi olan tek ki\u015fi siz olursunuz.<\/li>\n<li>Di\u011fer bir se\u00e7enek ise, \u00f6zel anahtar\u0131 yedeklemek i\u00e7in bir tohum c\u00fcmlesi gerektirmeyen so\u011fuk bir kripto c\u00fczdan\u0131 kullanmakt\u0131r. \u00d6rne\u011fin <a href=\"https:\/\/tangem.com\/\" target=\"_blank\" rel=\"nofollow noopener\">Tangem <\/a>donan\u0131m c\u00fczdan\u0131 bu \u015fekilde \u00e7al\u0131\u015f\u0131r.<\/li>\n<\/ol>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-generic\">\n","protected":false},"excerpt":{"rendered":"<p>2011-2015 y\u0131llar\u0131 aras\u0131nda \u00e7evrimi\u00e7i platformlarda olu\u015fturulan Bitcoin c\u00fczdanlar\u0131, anahtar olu\u015fturma k\u00fct\u00fcphanesindeki bir g\u00fcvenlik a\u00e7\u0131\u011f\u0131 nedeniyle g\u00fcvensiz olabilir.<\/p>\n","protected":false},"author":2706,"featured_media":11906,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1351],"tags":[374,1097,1098,2688,790,1590,2284,1500,2620,1831],"class_list":{"0":"post-11903","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-blok-zinciri","11":"tag-btc","12":"tag-guvenlik-aciklari","13":"tag-kripto-cuzdan","14":"tag-kripto-cuzdanlar","15":"tag-kripto-para-birimleri","16":"tag-kripto-para-cuzdanlari","17":"tag-kripto-paralar"},"hreflang":[{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/11903\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/26702\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/22125\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/11229\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/29456\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/26984\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/26892\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/29453\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/28286\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/36592\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/49943\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/21291\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/22070\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/30738\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/vulnerability-in-hot-cryptowallets-from-2011-2015\/35364\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/28948\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/vulnerability-in-hot-cryptowallets-from-2011-2015\/27215\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/32975\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/vulnerability-in-hot-cryptowallets-from-2011-2015\/32624\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com.tr\/blog\/tag\/kripto-paralar\/","name":"kripto paralar"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/11903","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/users\/2706"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=11903"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/11903\/revisions"}],"predecessor-version":[{"id":11909,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/11903\/revisions\/11909"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/media\/11906"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=11903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=11903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=11903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}