{"id":12862,"date":"2016-08-30T11:50:05","date_gmt":"2016-08-30T15:50:05","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=12862"},"modified":"2019-11-15T06:53:58","modified_gmt":"2019-11-15T11:53:58","slug":"bye-bye-lurk","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/bye-bye-lurk\/12862\/","title":{"rendered":"Lurk: Seek and destroy"},"content":{"rendered":"<p>Perhaps the biggest problem with cybercriminals is that they are extremely difficult to catch. Think of a real-life bank robbery with guns and face-masks \u2014 the thieves leave fingerprints; their voices are recorded by security cameras; police can trace their cars using traffic cameras; and so on. All of that helps the investigators find the suspects. But when cybercriminals pull off a robbery, they leave \u2026 basically nothing. No clues.<\/p>\n<p>Yet sometimes they get caught. Remember the <a href=\"https:\/\/www.kaspersky.com\/blog\/the-big-four-banking-trojans\/2956\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">SpyEye banking trojan<\/a>? Its creators were caught in 2011. Remember the Carberp group, which was active from 2010 to 2012? Caught as well. How about the infamous Angler exploit kit, which <a href=\"https:\/\/threatpost.com\/nuclear-angler-exploit-kit-activity-has-disappeared\/118842\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">suddenly went off the radar<\/a> in late June? Lurk malware stopped its attacks around the same time \u2014 because the group behind it <a href=\"https:\/\/securelist.com\/analysis\/publications\/75944\/the-hunt-for-lurk\/\" target=\"_blank\" rel=\"noopener noreferrer\">got caught<\/a>, with the help of Russian authorities and Kaspersky Lab.<\/p>\n<p>The story began back in 2011, when we first encountered Lurk. What caught our eye was the fact that some nameless Trojan that used remote banking software to steal money was classified by our internal malware naming system as a Trojan that could be used for many things \u2014 but not stealing money. So we took a closer look.<\/p>\n<p>The investigation yielded almost no results \u2014 the Trojan seemed to do nothing. But the attacks continued, and our analysts were able to get more and more samples to look at.<\/p>\n<p>During that time, we learned a lot about Lurk. For example, it had a modular structure: When the Trojan detected that it had infected a computer with remote banking software installed, it would download the malicious payload, which was responsible for stealing money. That is why our naming system didn\u2019t call Lurk a banking Trojan at first \u2014 the payload was missing.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">A technical look at <a href=\"https:\/\/twitter.com\/hashtag\/Lurk?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#Lurk<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/banking?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#banking<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/Trojan?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#Trojan<\/a> <a href=\"https:\/\/t.co\/rNsJ0YHimW\" target=\"_blank\" rel=\"noopener nofollow\">https:\/\/t.co\/rNsJ0YHimW<\/a> <a href=\"https:\/\/t.co\/vT7YLXZOae\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/vT7YLXZOae<\/a><\/p>\n<p>\u2014 Kaspersky (@kaspersky) <a href=\"https:\/\/twitter.com\/kaspersky\/status\/741267581676486656?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">June 10, 2016<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>We also found that Lurk avoided leaving any footprints on the hard drive, working only in the RAM of the computers it had infected. That made it harder to catch. Lurk\u2019s creators were also using encryption here and there as well as obfuscation. Their <a href=\"https:\/\/en.wikipedia.org\/wiki\/command_and_control_(malware)\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">command-and-control<\/a> servers were hosted on domains that were registered with false registration data. And the software \u2014 both Lurk\u2019s body and the malicious payloads \u2014 were constantly changing, being tailored specifically for one bank or another.<\/p>\n<p>Lurk\u2019s creators were careful, and we knew there must be a team of professionals behind such complex malware. But professionals are still just people, and people make mistakes. Those mistakes gave us information we could use to find the people behind the Trojan.<\/p>\n<p>Lurk, it turned out, was created and maintained by a group of about 15 people, although by the time it was shut down, that number had risen to 40. They had two projects: the malware itself and the botnet used for its distribution. Each project had its own team.<\/p>\n<p>A group of programmers developed Lurk, and a group of testers checked how it performed in various environments. On the botnet side, there were administrators, operators, a money flow manager, and other people. Money mules picked up cash at ATMs, and a money mule manager collected that money from the mules.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2016\/08\/06021643\/lurk-structure.png\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-12864\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2016\/08\/06021643\/lurk-structure.png\" alt=\"Lurk: Seek and destroy\" width=\"2000\" height=\"2000\"><\/a><\/p>\n<p>Most of the people involved were basically wage workers on a salary. To hire them, the people behind Lurk posted job vacancies on head-hunting websites, promising remote work with full employment and an attractive salary. During the job interview, the recruiter would ask the candidates whether they had strong moral principles. Those who didn\u2019t got the job.<\/p>\n<p>Developing Lurk and maintaining the botnet required not only a lot of people, but also some costly infrastructure including servers, VPNs, and other tools. After a few years in business, the Lurk team looked like a medium-size IT company. And like many companies, they decided to diversify their business after a while.<\/p>\n<p>The cybercriminals behind Lurk are also responsible for creating Angler, aka XXX \u2014 one of the most sophisticated exploit kits to date. At first it was designed as a tool to deliver Lurk to its victims, but its creators decided to sell Angler to third parties as well. Its success and apparent invincibility boosted the group behind Lurk to almost legendary status among Russian cybercriminals, and that in turn gave a good boost to Angler sales on underground markets.<\/p>\n<p>Angler became quite popular among cybercriminals. For example, it was used to distribute <a href=\"https:\/\/www.kaspersky.com\/blog\/cryptxxx-ransomware\/11939\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">CryptXXX<\/a> and <a href=\"https:\/\/www.kaspersky.com\/blog\/teslacrypt-ransomware-targets-gamers\/8021\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Teslacrypt<\/a> ransomware.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\"><a href=\"https:\/\/twitter.com\/hashtag\/Nuclear?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#Nuclear<\/a>, <a href=\"https:\/\/twitter.com\/hashtag\/Angler?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#Angler<\/a> exploit kit activity has disappeared via <a href=\"https:\/\/twitter.com\/threatpost?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">@threatpost<\/a> <a href=\"https:\/\/t.co\/XHxKsObx03\" target=\"_blank\" rel=\"noopener nofollow\">https:\/\/t.co\/XHxKsObx03<\/a> <a href=\"https:\/\/t.co\/GPjzpJDVvS\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/GPjzpJDVvS<\/a><\/p>\n<p>\u2014 Kaspersky (@kaspersky) <a href=\"https:\/\/twitter.com\/kaspersky\/status\/745789746245439492?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">June 23, 2016<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>But by the time they started to sell Angler, the group\u2019s days were already numbered. The Russian police, with Kaspersky Lab\u2019s help, had collected enough evidence to arrest the suspected group members. In June 2016 Lurk activity stopped, and soon Angler followed suit. The cybercriminals thought to the end that they would never get caught because of the precautions they took.<\/p>\n<p>Their precautions shielded them for a while, but even clever cybercriminals are still human. Sooner or later they\u2019ll stumble and make some mistakes, and then a good team of investigators will find them. It usually takes a long time and a lot of effort, but that\u2019s how we bring justice to the cyberworld.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How Kaspersky Lab helped the Russian police catch the cybercriminals behind the Lurk banking Trojan and Angler exploit kit.<\/p>\n","protected":false},"author":696,"featured_media":12863,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5,2683],"tags":[1781,734,93,1224,352,1780,772],"class_list":{"0":"post-12862","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"category-threats","9":"tag-angler","10":"tag-banking-trojans","11":"tag-cybercriminals","12":"tag-exploit-kit","13":"tag-kaspersky-lab","14":"tag-lurk","15":"tag-police"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/bye-bye-lurk\/12862\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/bye-bye-lurk\/7583\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/bye-bye-lurk\/7601\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/bye-bye-lurk\/9006\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/bye-bye-lurk\/8869\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/bye-bye-lurk\/12924\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/bye-bye-lurk\/6018\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/bye-bye-lurk\/6571\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/bye-bye-lurk\/8554\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/bye-bye-lurk\/12393\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/bye-bye-lurk\/12924\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/bye-bye-lurk\/12862\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/bye-bye-lurk\/12862\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/angler\/","name":"Angler"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/12862","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\/696"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=12862"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/12862\/revisions"}],"predecessor-version":[{"id":30169,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/12862\/revisions\/30169"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/12863"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=12862"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=12862"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=12862"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}