{"id":2552,"date":"2014-09-11T16:34:41","date_gmt":"2014-09-11T16:34:41","guid":{"rendered":"http:\/\/kasperskydaily.com\/b2b\/?p=2552"},"modified":"2019-11-15T07:13:01","modified_gmt":"2019-11-15T12:13:01","slug":"clustertrouble-dealing-with-a-multistage-financial-attack","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/clustertrouble-dealing-with-a-multistage-financial-attack\/2552\/","title":{"rendered":"Clustertrouble: dealing with a multistage financial attack"},"content":{"rendered":"<p>This is a story from our GERT group which is tasked with specific incident investigations. While the kind of work they do is far from being routine, it is mostly technical. So an attempt to tell a story about their investigations, for the most part, produces something overloaded with technical details: software names, malware aliases, ports, code fragments, etc. It\u2019s not always\u00a0interesting. This particular story is something special.<\/p>\n<p style=\"text-align: center\">\n<\/p><p>Okay, here\u2019s the plot. Some time ago, one company \u2013 large enough to operate with 5-6 digit sums \u2013 approached Kaspersky Lab\u2019s experts asking that we take a look at something wicked going on. In a nutshell, the bank it was working with requested they confirm a large outgoing payment. Trouble was, that payment was not supposed to be happening at all. The account manager responsible for making these payments was out to dinner at the time of the transaction attempt. Yet another \u2013 ten times smaller (but still rather large) \u2013 payment had been conducted already without alarming the bank. Again, without anyone in the firm aware of it.<\/p>\n<blockquote class=\"twitter-pullquote\"><p>Clustertrouble: dealing with a multistage financial attack #enterprisesec #protectmybiz<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2Fh8jR&amp;text=Clustertrouble%3A+dealing+with+a+multistage+financial+attack+%23enterprisesec+%23protectmybiz\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>The situation smelled foul enough for the company representatives to suspect there was malware at play. That suspicion was confirmed in the very first days of investigation. And it was quite impressive, something out of the \u201crough-but-effective\u201d sort. Even though the hackers made one big mistake.<\/p>\n<p>The experts at Kaspersky Lab\u2019s Global Emergency Response Team (GERT) received an image of the attacked computer\u2019s hard drive from the attacked organization, studied this and soon detected a suspicious email message sent allegedly from the state tax office, asking to provide some documents immediately.<\/p>\n<p style=\"text-align: center\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2014\/09\/06020128\/wide-4-1.png\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-2554\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2014\/09\/06020128\/wide-4-1.png\" alt=\"wide-4\" width=\"1000\" height=\"665\"><\/a><\/p>\n<p>Actually that message header was written in capital letters and with a lot of exclamation points, which isn\u2019t exactly a style of an official letter from a government agency. So it really should raise suspicions. Apparently the accountant was sort of mesmerized with the words \u201cFederal tax service\u201d. By the way, names and addresses of the tax service officers in the message were real and legit.<\/p>\n<p>All in all, the document had been opened, thus setting loose Exploit.MSWord.CVE-2012-0158. The exploit then downloaded an archived file from a remote system, which in turn yielded Backdoor.Win32.RMS. This backdoor was used to monitor the accountant activities for a couple of days. Then two more pieces of malware had been downloaded using that backdoor \u2013 a keylogger Trojan-Spy.Win32.Delf and Backdoor.Win32.Agent. The keylogger had been used to hijack the accountant\u2019s password to banking software, second Backdoor \u2013 to hijack the PC itself and operate on it remotely. Gotcha.<\/p>\n<p>That\u00a0wasn\u2019t all. When the investigation was nearing completion, the experts discovered yet another curious fact: Attackers rolled out a special network of C&amp;C servers to control their malware, but made a mistake which allowed Kaspersky Lab\u2019s experts to find out the IP addresses of other computers infected with Trojan-Spy.Win32.Delf.<\/p>\n<p>In most cases, these proved to be computers owned by SMBs. Kaspersky Lab promptly contacted the owners of the infected computers and warned them of the threat.<\/p>\n<blockquote class=\"twitter-pullquote\"><p>Had there be no warning from the bank, the losses would be dramatic. #enterprisesec<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2Fh8jR&amp;text=+Had+there+be+no+warning+from+the+bank%2C+the+losses+would+be+dramatic.+%23enterprisesec+\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>This last circumstance raises yet another problem: how often do criminals infect one company\u2019s network in order to successfully attack another? The first company may be completely clueless about the malware operating on and from its servers (or even some more exotic places such as wireless modems, for instance, why not?), and stay undetected for quite some time. Once again it becomes obvious that cybersecurity is everybody\u2019s business.<\/p>\n<p>And one more thing. There are technical details. A lot of them. Feel free to find them <a href=\"https:\/\/securelist.com\/analysis\/publications\/66454\/thefts-in-remote-banking-systems-incident-investigations\/\" target=\"_blank\" rel=\"noopener\">here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A curious story about a cyber-investigation of fraudulent activities, which our GERT group had recently conducted on behalf of one of the company&#8217;s clients. The attackers were quite thoughtful, but not good enough.<\/p>\n","protected":false},"author":209,"featured_media":15837,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[2180,282,2181,2182,36],"class_list":{"0":"post-2552","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-cyber-investigation","10":"tag-cybersecurity","11":"tag-fraudulent-payments","12":"tag-gert","13":"tag-malware-2"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/clustertrouble-dealing-with-a-multistage-financial-attack\/2552\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/clustertrouble-dealing-with-a-multistage-financial-attack\/2552\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/clustertrouble-dealing-with-a-multistage-financial-attack\/2552\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/cyber-investigation\/","name":"cyber-investigation"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/2552","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=2552"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/2552\/revisions"}],"predecessor-version":[{"id":30718,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/2552\/revisions\/30718"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/15837"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=2552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=2552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=2552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}