{"id":9790,"date":"2017-11-03T13:00:46","date_gmt":"2017-11-03T09:00:46","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/?p=9790"},"modified":"2019-11-15T15:23:41","modified_gmt":"2019-11-15T11:23:41","slug":"cryptocurrencies-intended-risks","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/cryptocurrencies-intended-risks\/9790\/","title":{"rendered":"Problems and risks of cryptocurrencies"},"content":{"rendered":"<p>Cryptocurrencies are basically the same as e-money \u2014 like WebMoney or PayPal. That means they also have the same problems as classic e-payment systems.<\/p>\n<p>However, the operating principles specific to cryptocurrencies sometimes make the problems more likely to occur, and thus more disturbing. In addition, the same principles are responsible for a certain number of risks unique to cryptocurrencies.<\/p>\n<h3>Spoofing payment information and phishing<\/h3>\n<p>We\u2019ll start with common problems such as plain old theft. Let\u2019s say you\u2019re transferring money to a friend. You copy his wallet address accurately, but <a href=\"https:\/\/www.kaspersky.com\/blog\/cryptoshuffler-bitcoin-stealer\/19976\/\" target=\"_blank\" rel=\"noopener nofollow\">malware replaces the address in the clipboard with another one<\/a>. Not every user is vigilant and double checks an address after copying it. Especially if the address is a long jumble of characters.<\/p>\n<p>Or take phishing, for another example. As with ordinary e-money, users can be tricked into going to a phishing website where they upload their cryptowallets and enter a password.<\/p>\n<p>Of course, users of a traditional bank or payment system can also run into trouble with cyberthieves. However, with a traditional system there is always a fairly good chance of canceling the transfer. In the case of cryptocurrencies, you might as well try to complain to the United Nations. What happens in blockchain stays in blockchain.<\/p>\n<h3>Hacking a payment gateway<\/h3>\n<p>On top of that, even using a genuine payment gateway with the correct address can result in a loss of money. In June 2017, the most popular Web wallet for the Ethereum Classic cryptocurrency, with the original address <a href=\"https:\/\/classicetherwallet.com\/\" target=\"_blank\" rel=\"noopener nofollow\">https:\/\/classicetherwallet.com\/<\/a>, suddenly <a href=\"https:\/\/www.bleepingcomputer.com\/news\/security\/classic-ether-wallet-hacked-users-report-massive-losses\/\" target=\"_blank\" rel=\"noopener nofollow\">started stealing money<\/a> from users\u2019 wallets.<\/p>\n<p>Turned out, hackers had used social-engineering methods to convince the hosting provider that they were the real domain owners. After gaining access, they started intercepting cash flows.<\/p>\n<p>Luckily, the strategy those hackers used wasn\u2019t the best \u2014 they replaced the payees immediately, thus quickly blowing their cover and managing to steal only $300,000 in several hours. If they had collected the wallets and waited a while, they would have remained undetected for a lot longer, and the damage probably would have been far worse.<\/p>\n<p>In all fairness, classic financial services can also fall prey to that kind of attack. For example, in Brazil this year, hackers <a href=\"https:\/\/www.wired.com\/2017\/04\/hackers-hijacked-banks-entire-online-operation\/\" target=\"_blank\" rel=\"noopener nofollow\">hijacked a whole bank<\/a>.<\/p>\n<h3>User address error<\/h3>\n<p>The preceding cases were typical electronic-money issues, but as we\u2019ve already said, cryptocurrencies add their own wrinkles. For example, there is a risk that\u2019s very specific to cryptocurrencies \u2014 loss of money due to an error in the address to which the money transfer is made.<\/p>\n<p>In the case of Ethereum, if the last digit of the address wasn\u2019t copied, the money would disappear into thin air. Or it would go where it was supposed to, but the amount you intended to transfer would be it <a href=\"http:\/\/vessenes.com\/the-erc20-short-address-attack-explained\/\" target=\"_blank\" rel=\"noopener nofollow\">multiplied by 256<\/a>.<\/p>\n<p>That error is not relevant to Bitcoin; its system has built-in address validation. However, in Bitcoin, you might send money to a mystery recipient \u2014 how does losing <a href=\"https:\/\/www.reddit.com\/r\/Bitcoin\/comments\/273vi2\/if_you_just_received_800_bitcoin_out_of_the_blue\/\" target=\"_blank\" rel=\"noopener nofollow\">800 bitcoins<\/a> strike you? (that\u2019s about $3.2 million at the exchange rate on September 28, 2017). Or you could unwittingly pay a fee of <a href=\"https:\/\/blockchain.info\/tx\/258478e8b7a3b78301661e78b4f93a792af878b545442498065ab272eaacf035\" target=\"_blank\" rel=\"noopener nofollow\">80 bitcoins<\/a> (about $320,000). To be fair, that kind of mistake is unlikely with a popular Bitcoin client; in those cases it\u2019s likely people were using something homemade.<\/p>\n<h3>Loss of a wallet file<\/h3>\n<p>There\u2019s one more problem that is typical of cryptocurrencies: loss or theft of a wallet. Most users store their cryptocurrency wallet files on their computers. Therefore, they can be <a href=\"http:\/\/www.zdnet.com\/article\/now-cerber-ransomware-wants-to-steal-your-bitcoin-wallets-and-passwords-too\/\" target=\"_blank\" rel=\"noopener nofollow\">stolen using malware<\/a> or lost if the hard disk crashes.<\/p>\n<p>So most advanced users make hard copies of their secret key and purchase USB hardware wallets. But the number of such users is small.<\/p>\n<p>The situation with \u201ccentralized\u201d e-money is far better at present. It\u2019s the rare Internet bank that doesn\u2019t require two-factor authentication and confirmation of transactions using SMS with one-time-use passwords. And in the case of corporations or large amounts, the use of a USB token is mandatory.<\/p>\n<h3>Insecure ICOs<\/h3>\n<p>In 2017, investing in projects associated with a blockchain or cryptocurrencies became very popular among cryptocurrency holders. This type of fundraising is called an ICO \u2014 Initial Coin Offering.<\/p>\n<p>You can learn more about how all this happens, <a href=\"https:\/\/www.kaspersky.com\/blog\/ethereum-ico\/\" target=\"_blank\" rel=\"noopener nofollow\">what the Ethereum network is, and how smart contracts work<\/a>, in our previous post on the topic, so we won\u2019t repeat the technical details here. The upshot is that using cryptocurrencies has made it easy to raise outrageous amounts of funds with nothing more than an Internet connection. More than $1.7 billion has already been raised through ICOs in 2017. You don\u2019t hear much about successful projects, but investors are still optimistic.<\/p>\n<p>What\u2019s the problem, then? The problem is that the cryptocurrency market still isn\u2019t regulated by any means, there are no risk assessment mechanisms, and there is no guarantee \u2014 like at all \u2014 of return on investments, except the word of honor of people who came up with the project.<\/p>\n<p>Generally speaking, the fact that someone has an idea doesn\u2019t mean the idea is good or even feasible, that the resulting product will make a profit, or that the author will actually spend the money on implementing it rather than on paying the director (himself). Ultimately, he might simply make off with the money, knowing it\u2019s not very easy to track down and de-anonymize a payee on the cryptocurrency market.<\/p>\n<h3>Spoofing a user address<\/h3>\n<p>Sometimes, a money-grabbing scheme is even simpler. Collection of funds in an ICO usually opens at a specified time and closes when the required amount has been collected. The collection address is posted on the project website when it opens (it\u2019s not necessary, just common practice).<\/p>\n<p>During one ICO, a hacker got access to the project website and as soon as collection opened, <a href=\"https:\/\/www.coindesk.com\/7-million-ico-hack-results-coindash-refund-offer\/\" target=\"_blank\" rel=\"noopener nofollow\">he replaced the address with his own<\/a>. Within an hour, 2,000 participants had thrown in $8 million. Then the address was flagged as fake. But even that didn\u2019t stop the eager crypto-investors \u2014 a lot of them continued to transfer money to the same fake address, and the hacker got another $2 million that day.<\/p>\n<h3>Tips for cryptocurrency holders and crypto-investors<\/h3>\n<p>How can you avoid the abovementioned problems? We have several tips to help.<\/p>\n<ol>\n<li>Always verify a Web wallet\u2019s address, and don\u2019t follow links to an Internet bank or Web wallet.<\/li>\n<li>Before sending, double-check the recipient\u2019s address (at least check the first and last characters), the amount being sent, and the size of the associated fee.<\/li>\n<li>Write down a mnemonic phrase that allows you to recover a cryptowallet if you lose it or forget your password.<\/li>\n<li>Keep a cool head and make informed decisions when crypto-investing, and don\u2019t panic or hurry.<\/li>\n<li>Always remember that crypto-investment is very risky. Do not invest more than you\u2019re ready to lose at any moment. Diversify your investments.<\/li>\n<li>Use cryptocurrency hardware wallets.<\/li>\n<li>Run high-quality antivirus protection to protect the devices you use to access cryptowallets, trade on crypto-exchanges, and so on.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Along with economic benefits, any new technology also comes with a certain number of problems. Cryptocurrencies are no exception.<\/p>\n","protected":false},"author":669,"featured_media":9791,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1226],"tags":[374,1161,1308,1505,1504,1507,321,521],"class_list":{"0":"post-9790","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"tag-bitcoin","9":"tag-bitcoins","10":"tag-blockchain","11":"tag-cryptocurrencies","12":"tag-ethereum","13":"tag-ico","14":"tag-technology","15":"tag-threats"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/cryptocurrencies-intended-risks\/9790\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/cryptocurrencies-intended-risks\/11752\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/cryptocurrencies-intended-risks\/13174\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/cryptocurrencies-intended-risks\/12072\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/cryptocurrencies-intended-risks\/11672\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/cryptocurrencies-intended-risks\/14733\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/cryptocurrencies-intended-risks\/14407\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/cryptocurrencies-intended-risks\/19136\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/cryptocurrencies-intended-risks\/4406\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/cryptocurrencies-intended-risks\/20034\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/cryptocurrencies-intended-risks\/9745\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/cryptocurrencies-intended-risks\/9917\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/cryptocurrencies-intended-risks\/15181\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/cryptocurrencies-intended-risks\/8832\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/cryptocurrencies-intended-risks\/18610\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/cryptocurrencies-intended-risks\/19024\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/cryptocurrencies-intended-risks\/19017\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/bitcoin\/","name":"bitcoin"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/9790","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/669"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=9790"}],"version-history":[{"count":3,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/9790\/revisions"}],"predecessor-version":[{"id":14793,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/9790\/revisions\/14793"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/9791"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=9790"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=9790"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=9790"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}