{"id":16645,"date":"2020-04-30T13:13:48","date_gmt":"2020-04-30T17:13:48","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/shade-decryptor-2020\/16645\/"},"modified":"2020-05-04T16:46:02","modified_gmt":"2020-05-04T12:46:02","slug":"shade-decryptor-2020","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/shade-decryptor-2020\/16645\/","title":{"rendered":"Decrypt all strains of Shade ransomware"},"content":{"rendered":"<p>Remember Shade ransomware? We\u2019re writing this post because it\u2019s not a threat anymore, and you can get your files back, even those encrypted by the latest versions of Shade. Let\u2019s talk about how that happened.<\/p>\n<h2>What is Shade ransomware?<\/h2>\n<p>Shade, also known as Troldesh, is a nasty cryptor that began spreading back in 2015. It encrypted office documents, pictures, and archives (as well as some other types of files) and then asked victims to pay for decryption. Different strains used fancy filenames such as breaking_bad and da_vinci_code. Shade also brought friends along \u2014 it downloaded other malware after it encrypted everything it wanted.<\/p>\n<p>In 2016, our malware analysts managed to <a href=\"https:\/\/www.kaspersky.com\/blog\/shade-decryptor\/12661\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">create a decryptor for the versions of Shade that existed back then<\/a>. Cooperation between police, having seized the servers with the keys, and the security researchers, made that possible.<\/p>\n<p>However, the group behind Shade didn\u2019t go anywhere and continued to develop new strains of ransomware for which the decryptor didn\u2019t work. The malefactors continued to spread Shade, remaining highly active through mid-2019.<\/p>\n<h2>The group behind Shade<\/h2>\n<p>Things eventually changed. In late 2019 and early 2020 the number of users that encountered Shade ransomware dropped significantly in comparison with previous years. And then the malefactors behind the ransomware announced that they had decided to abandon it. They even apologized for the harm they caused and <a href=\"https:\/\/github.com\/shade-team\/keys\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">published<\/a> about 750,000 keys to decrypt the files.<\/p>\n<div class=\"infogram-embed\" data-id=\"_\/GuDlnEXM1a4vrjeoO8Yf\" data-type=\"interactive\" data-title=\"Shade Ransomware\"><\/div>\n<p><script>!function(e,n,i,s){var d=\"InfogramEmbeds\";var o=e.getElementsByTagName(n)[0];if(window[d]&&window[d].initialized)window[d].process&&window[d].process();else if(!e.getElementById(i)){var r=e.createElement(n);r.async=1,r.id=i,r.src=s,o.parentNode.insertBefore(r,o)}}(document,\"script\",\"infogram-async\",\"https:\/\/e.infogram.com\/js\/dist\/embed-loader-min.js\");<\/script><\/p>\n<p>That\u2019s a good reason to update the decryption utility, which is exactly what we did. The <a href=\"https:\/\/support.kaspersky.com\/13059?_ga=2.27044596.858346383.1588243768-313061628.1558015910\" target=\"_blank\" rel=\"noopener noreferrer\">new Shade decryptor<\/a> is now available on <a href=\"http:\/\/noransom.kaspersky.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">noransom.kaspersky.com<\/a>, and it can help people get back their files encrypted by Shade, no matter which version of Shade got them into trouble.<\/p>\n<p>Remember, we\u2019re always saying that you <a href=\"https:\/\/www.kaspersky.com\/blog\/no-no-ransom\/13364\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">should not pay the ransom even<\/a> if there is no decryptor to get them back at the moment, because eventually it will be created. This is an example of such a case, and it\u2019s a great example of why you should hold on to your encrypted files and wait, even if you have been hit by some other type of ransomware. One day, the decryptor will exist.<\/p>\n<h2>Better safe than rescued<\/h2>\n<p>It\u2019s good that all the victims of Shade can now get their files back. However, it would\u2019ve been better for them not to lose the files in the first place. So, here are our usual three tips that will help you not fall victim to ransomware:<\/p>\n<ul>\n<li>Make regular backups. <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-backup\/19589\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Here\u2019s how to do that right<\/a>.<\/li>\n<li>Don\u2019t click on suspicious links, and don\u2019t open attachments to e-mails from unknown senders. Basically, use common sense and learn. Once you know the usual attack vectors, avoiding threats like Shade becomes second nature.<\/li>\n<li>Use a <a href=\"https:\/\/me-en.kaspersky.com\/plus?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kplus___\" target=\"_blank\" rel=\"noopener\">good security solution<\/a>. Even if you think you\u2019re really good at spotting potential threats, a reliable security solution will help if once in a thousand times you miss one \u2014 just like the tightrope-walker still has that safety line attached, even though they\u2019ve walked that rope a thousand times before.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-ransomware\">\n","protected":false},"excerpt":{"rendered":"<p>Kaspersky researchers publish a decryptor that can help get back files encrypted by all strains of Shade\/Troldesh ransomware.<\/p>\n","protected":false},"author":2581,"featured_media":16666,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1486],"tags":[1239,1203,433,2286],"class_list":{"0":"post-16645","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-decryptors","9":"tag-noransom","10":"tag-ransomware","11":"tag-shade"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/shade-decryptor-2020\/16645\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/shade-decryptor-2020\/21140\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/shade-decryptor-2020\/8203\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/shade-decryptor-2020\/22168\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/shade-decryptor-2020\/19892\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/shade-decryptor-2020\/18610\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/shade-decryptor-2020\/22618\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/shade-decryptor-2020\/21534\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/shade-decryptor-2020\/28311\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/shade-decryptor-2020\/8188\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/shade-decryptor-2020\/35246\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/shade-decryptor-2020\/14794\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/shade-decryptor-2020\/15155\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/shade-decryptor-2020\/13417\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/shade-decryptor-2020\/23912\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/shade-decryptor-2020\/11416\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/shade-decryptor-2020\/28239\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/shade-decryptor-2020\/25387\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/shade-decryptor-2020\/22204\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/shade-decryptor-2020\/27484\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/shade-decryptor-2020\/27319\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/ransomware\/","name":"ransomware"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/16645","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\/2581"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=16645"}],"version-history":[{"count":1,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/16645\/revisions"}],"predecessor-version":[{"id":16665,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/16645\/revisions\/16665"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/16666"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=16645"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=16645"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=16645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}