{"id":15137,"date":"2016-04-20T15:27:28","date_gmt":"2016-04-20T15:27:28","guid":{"rendered":"https:\/\/kasperskydaily.com\/b2b\/?p=5470"},"modified":"2019-11-15T06:57:40","modified_gmt":"2019-11-15T11:57:40","slug":"ransomfails","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/ransomfails\/15137\/","title":{"rendered":"Ransomfails: a few stories on beating cryptors"},"content":{"rendered":"<p>In recent months, we have had a number of stories, grim and dreary, about the perils of ransomware. For a change \u2013 and for a little bit of amusement \u2013 we\u2019d like to offer a few tales about defeating ransomware.<\/p>\n<p><strong>\u201cHelpme\/file2\u201d<\/strong><\/p>\n<p>This ransomware was only known by names \u201chelpme@freespeechmail.org\u201d and \u201cfile2@openmailbox.org,\u201d after two of the email addresses users were told to contact the malware\u2019s author and to receive payment details for possible decryption.<\/p>\n<p>Author(s) demanded three bitcoins as a fee. Tech forums and outlets called that ransomware extremely nasty as it had caused a lot of destruction.<\/p>\n<blockquote class=\"twitter-pullquote\"><p>Ransomfails: a few stories on beating #cryptors<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2F8uK3&amp;text=Ransomfails%3A+a+few+stories+on+beating+%23cryptors\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>However, in the Fall of\u00a0last year it was <a href=\"http:\/\/sensorstechforum.com\/forums\/malware-removal-questions-and-guides\/decrypt-files-encrypted-by-helpmefreespeechmail-org-ransomware-virus\/\" target=\"_blank\" rel=\"noopener nofollow\">discovered<\/a>\u00a0that this ransomware is prone to brute-force using Kaspersky Lab\u2019s <a href=\"http:\/\/support.kaspersky.com\/us\/viruses\/disinfection\/10556\" target=\"_blank\" rel=\"noopener\">RakhniDecryptor<\/a> utility. It was intended to crack the \u201cvenerable\u201d Rakhni (Trojan-Ransom.Win32.Rakhni) cryptor known since 2013. Most likely \u201chelpme@freespeechmail\u201d ransomware is a derivative of the former.<\/p>\n<p>So in the end, it is quite possible to give the criminals the sack, not ransom.<\/p>\n<p><strong>The failure epique of DMA cryptor<\/strong><\/p>\n<p>An encrypting malware of Polish origin, this one initially featured a ransom note only in Polish. However, with time DMA\u2019s code improved and the English ransom notes were added.<\/p>\n<p>Then researchers from Malwarebytes decided to <a href=\"http:\/\/news.softpedia.com\/news\/dual-mode-dma-ransomware-cracked-users-can-recover-files-for-free-499848.shtml\" target=\"_blank\" rel=\"noopener nofollow\">go in<\/a>, and found a lot of funny things about DMA.<\/p>\n<p>Funny thing one: malware authors advertised that they used an AES-256 key to encrypt files and then secured that key via an RSA-2048 cipher, but then researchers discovered that it only employed a custom encryption algorithm, which was quickly cracked.<\/p>\n<p>Funny thing two: DMA had no protection against reverse engineering, which was excellent news for the researchers.<\/p>\n<p>Funny thing three: DMA encryption key came hard-coded in one of its binaries.<\/p>\n<p>Funny thing four: DMA author embedded the decrypter right inside the ransom note, creating dual-mode ransomware that can encrypt and decrypt files from the same source code.<\/p>\n<p>Even if those smarties who wrote DMA found out they made a mistake by embedding the decryption, their custom encryption algorithm is still a weak one. Fortunately for the victims, it\u2019s an amateur\u2019s work that\u2019s not going to be much of a danger.<\/p>\n<p><strong>Petya ransomware rocked-n-busted<\/strong><\/p>\n<p>A nefarious cryptor codenamed Petya (a Russian counterpart for name Pete) had been discovered late last month. It had a peculiar feature: it targeted infected machine\u2019s master boot records, and the only option for the victims was to hand over roughly $400 in Bitcoin for the decryption key.<\/p>\n<p>A certain individual who goes by the handle @leostone posted an algorithm to generate decryption keys.<\/p>\n<blockquote class=\"twitter-pullquote\"><p>#Ransomware can be beaten, but it\u2019s more about luck and criminals\u2019 mistakes \u2013 not something reliable.<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2F8uK3&amp;text=%23Ransomware+can+be+beaten%2C+but+it%26%238217%3Bs+more+about+luck+and+criminals%26%238217%3B+mistakes+%26%238211%3B+not+something+reliable.\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>As<a href=\"https:\/\/threatpost.com\/password-generator-tool-breaks-petya-ransomware-encryption\/117315\/\" target=\"_blank\" rel=\"noopener nofollow\"> Threatpost points out<\/a>, users can generate a decryption key, providing they can supply the tool with information from their infected drive \u2013 the boot sector and nonce associated with it.<\/p>\n<p>This may be not an easy task for the average user, but Fabian Wosar, a security researcher at Emsisoft, created an executable over the weekend designed to extract data from infected Petya drives and expedite the process.<\/p>\n<p>The same Mr. Wosar just recently managed to crack the encryption of <a href=\"http:\/\/news.softpedia.com\/news\/hydracrypt-and-umbrecrypt-ransomware-cracked-decrypter-available-for-download-500345.shtml\" target=\"_blank\" rel=\"noopener nofollow\">HydraCrypt and UmbreCrypt ransomware families<\/a>.<\/p>\n<p>On Sunday, Lawrence Abrams, a computer forensics expert who blogs at BleepingComputer.com and has been following the ransomware\u2019s saga, put together a guide on how to use the tool. He tested it and successfully recovered the data from the test machine. However, he acknowledged that Petya authors may soon update their ransomware making decryption a much more complicated process.<\/p>\n<p><strong>You wanted to play a game? Really?<\/strong><\/p>\n<p>A sadistic ransomware wasn\u2019t just encrypting the files but also deleted them unless the victim paid 0.4 Bitcoin or $150 within an hour. Restarting a PC would also cost 1,000 deleted files.<\/p>\n<p>The ransom demand contained the image from the \u201cSaw\u201d horror movie franchise and an appropriate line \u201cI want to play a game with you\u2026\u201d<\/p>\n<p><a href=\"https:\/\/threatpost.com\/decryption-tool-stifles-jigsaw-ransomware\/117387\/\" target=\"_blank\" rel=\"noopener nofollow\">Game\u2019s over, at least for now<\/a>. Researchers, including security researchers at MalwareHunterTeam and individual computer forensics experts Michael Gillespie and Lawrence Abrams, have analyzed the malware and developed\u00a0a decryption tool that allows victims to recover their files for free.<\/p>\n<div id=\"attachment_5472\" style=\"width: 789px\" class=\"wp-caption aligncenter\"><img decoding=\"async\" aria-describedby=\"caption-attachment-5472\" class=\"wp-image-5472 size-full\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2016\/04\/06020451\/saw.jpg\" alt=\"saw\" width=\"779\" height=\"457\"><p id=\"caption-attachment-5472\" class=\"wp-caption-text\">Your game was unimpressive, clowns.<\/p><\/div>\n<p>Now the funniest thing: Jigsaw can be prevented from deleting any files if an affected user goes into their Windows Task Manager and terminates firefox.exe and all of the drpbx.exe processes. In fact Jigsaw gets into the system as a fake Firefox browser installation file.<\/p>\n<p>Then there\u2019s only an encryption problem, which is beaten by the aforementioned decryption tool.<\/p>\n<p><strong>Still not common<\/strong><\/p>\n<p>It\u2019s not common for ransomware criminals to be outsmarted. In fact, it is quite a rare occasion. More often users and businesses are facing less than exciting prospects of paying ransoms without a guarantee of getting their files back.<\/p>\n<p>Some strains of ransomware are plain impossible to decrypt without knowing the keys, simply because the encryption algorithm they use are too strong.<\/p>\n<p>So, by default it is much more reasonable to take preventive measures and not let the beasts in.<\/p>\n<p>Andrey Pozhogin <a href=\"https:\/\/business.kaspersky.com\/prevent-ransomware-from-destroying-your-fileshare\/5379\/\" target=\"_blank\" rel=\"noopener nofollow\">blogged a couple of weeks ago<\/a>:<\/p>\n<p><em>\u201cRemember the multi-layered approach to security. Backup religiously. Stop phishing at your email server or web browser. Stop known malware\u2026 Check with cloud intelligence. Let it boil a little in a sandbox. Let your firewall do some jobs for you. Make sure application privilege control stops applications from accessing your personal data unless explicitly allowed. Or go all the way and switch to Default Deny mode.\u201d<\/em><\/p>\n<p>It is way easier to prevent a fire than to extinguish it when it has already started.<\/p>\n<p>Also, take a look at Kaspersky Lab\u2019s recent release \u2013 <a href=\"https:\/\/business.kaspersky.com\/anti-cryptor\/5442\/\" target=\"_blank\" rel=\"noopener nofollow\">Kaspersky Security for Windows Server application<\/a>, enhanced with Anti-Cryptor technology, specifically to prevent \u201cransomfire\u201d from spreading all over.<\/p>\n<p>Stay safe!<\/p>\n<p>P.S. And drop us a comment or two about your own encounters with ransomware if there have been any!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s not common that the ransomware criminals can be outsmarted. But sometimes they can be.<\/p>\n","protected":false},"author":209,"featured_media":15414,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[1680,1639,420],"class_list":{"0":"post-15137","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-cryptors","10":"tag-ransom","11":"tag-ransomware"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/ransomfails\/15137\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/ransomfails\/8096\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/ransomfails\/3707\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/ransomfails\/15137\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/ransomfails\/15137\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/cryptors\/","name":"cryptors"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/209"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=15137"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15137\/revisions"}],"predecessor-version":[{"id":30285,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15137\/revisions\/30285"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/15414"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=15137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=15137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=15137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}