{"id":13624,"date":"2018-10-18T10:45:15","date_gmt":"2018-10-18T18:45:15","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/10\/18\/news-7391\/"},"modified":"2018-10-18T10:45:15","modified_gmt":"2018-10-18T18:45:15","slug":"news-7391","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2018\/10\/18\/news-7391\/","title":{"rendered":"The Mysterious Return of Years-Old APT1 Malware"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5bc7cbce4bb3fa2ced830b1d\/master\/pass\/chinese_malware_v2.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Thu, 18 Oct 2018 04:01:00 +0000<\/strong><\/p>\n<p><span class=\"lede\">In 2013, cybersecurity <\/span>firm Mandiant published <a href=\"https:\/\/www.wired.com\/2013\/02\/chinese-army-linked-to-hacks\/\">a blockbuster report<\/a> on a state-sponsored hacking team known as APT1, or Comment Crew. The Chinese group achieved instant infamy, tied to the successful hacks of more than 100 US companies and the exfiltration of hundreds of terabytes of data. They also vanished in the wake of being exposed. Now, years later, researchers from security firm McAfee say they\u2019ve found code based on APT1\u2013associated malware cropping up in a new set of attacks.<\/p>\n<p>Specifically, McAfee has found malware that reuses a portion of the code found in an implant called Seasalt, which APT1 introduced sometime around 2010. Lifting and repurposing pieces of malware is not an unusual practice, especially when those tools are widely available or open source. Look no further than the <a href=\"https:\/\/www.wired.com\/story\/eternalblue-leaked-nsa-spy-tool-hacked-world\/\">rash of attacks based on EternalBlue<\/a>, the <a href=\"https:\/\/www.wired.com\/story\/korea-accountable-wannacry-nsa-eternal-blue\/\">leaked NSA tool<\/a>. But source code used by APT1, McAfee says, never became public, nor did it wind up on the black market. Which makes its reappearance something of a mystery.<\/p>\n<p class=\"paywall\">\u201cWhen we picked up the samples and we found code reuse for Comment Crew,\u201d says McAfee chief scientist Raj Samani, \u201call of a sudden it was like an \u2018oh shit\u2019 moment.\u201d<\/p>\n<p class=\"paywall\">McAfee says it has seen five waves of attacks using the remixed malware, which it calls Oceansalt, dating back to May of this year. The attackers crafted spearphishing emails, with infected Korean-language Excel spreadsheet attachments, and sent them to targets who were involved in South Korean public infrastructure projects and related financial fields.<\/p>\n<p class=\"paywall\">\u201cThey knew the people to target,\u201d Samani says. \u201cThey had identified the targets that they needed to manipulate into opening these malicious documents.\u201d<\/p>\n<p>&quot;All of a sudden it was like an \u2018oh shit\u2019 moment.&quot;<\/p>\n<p name=\"inset-left\" class=\"inset-left-component__el\">Raj Samani, McAfee<\/p>\n<p class=\"paywall\">Victims who opened those documents unwittingly installed Oceansalt. McAfee believes the malware was used for initial reconnaissance, but had the ability to take control both of the system it infected and any network that device connected to. \u201cThe access that they had was quite significant,\u201d says Samani. \u201cEverything from getting full insight into the file structure, being able to create files, delete files, being about to list processes, terminate processes.\u201d<\/p>\n<p class=\"paywall\">While the initial attacks focused on South Korea\u2014and appear to have been instigated by people fluent in Korean\u2014they at some point spread to targets in the United States and Canada, focusing especially on the financial, health care, and agricultural industries. McAfee says it\u2019s not aware of any obvious ties between the impacted companies and South Korea, and that the move West may have been a separate campaign.<\/p>\n<p class=\"paywall\">McAfee does note some differences between Oceansalt and its precursor. Seasalt, for instance, had a persistence method that let it remain on an infected device even after a reboot. Oceansalt does not. And where Seasalt sent data to the control server unencrypted, Oceansalt employs an encoding and decoding process.<\/p>\n<p class=\"paywall\">Still, the two share enough code that McAfee is confident in the connection. It\u2019s far less certain, though, about who\u2019s behind it.<\/p>\n<p class=\"paywall\">It\u2019s hard to overstate just how capable APT1 was, and how unprecedented Mandiant\u2019s insights were at the time. \u201cAPT1 were extraordinarily prolific,\u201d says Benjamin Read, senior manager for cyberespionage analysis at FireEye, which <a href=\"https:\/\/www.fireeye.com\/company\/press-releases\/2014\/fireeye-announces-acquisition-of-mandiant.html\" target=\"_blank\">acquired Mandiant<\/a> in 2014. \u201cThey were one of the highest in terms of volume. But volume can also allow you to build a pattern of life. When you\u2019re doing that much stuff, you\u2019re going to have slip-ups that expose some of the backend.\u201d<\/p>\n<p class=\"paywall\">It\u2019s probably not accurate to say that APT1 disappeared after the Mandiant report. It\u2019s just as likely that the unit\u2019s hackers continued to work for China under a different guise. But it is true, Read says, that the tactics, the infrastructure, and specific malware associated with the group haven\u2019t seen the light of day in those five years.<\/p>\n<p class=\"paywall\">It\u2019s tempting to think, perhaps, that McAfee\u2019s find means that APT1 is back. But attribution is hard under any circumstances, and Oceansalt is no smoking gun. In fact, McAfee sees a few distinct possibilities as to its provenance.<\/p>\n<p class=\"paywall\">\u201cEither it\u2019s the re-emergence of this group, or potentially you\u2019re looking at state-to-state collaboration with regards to a major espionage campaign, or somebody\u2019s trying to point the finger at the Chinese,\u201d says Samani. \u201cEither one of those three scenarios is quite significant.\u201d<\/p>\n<p class=\"paywall\">Despite a <a href=\"https:\/\/www.wired.com\/story\/china-hacks-against-united-states\/\">mounting hacking threat from China<\/a>, McAfee\u2019s own report considers it \u201cunlikely\u201d that Oceansalt actually marks the return of APT1. Even assuming those hackers are still active somewhere in the Chinese system, why return to tools that had previously been exposed?<\/p>\n<p class=\"paywall\">Then there\u2019s the possibility that an actor has somehow acquired the code, either directly from China or through other unknown means. \u201cIt is possible, very possible, that this was potentially an intended collaboration. Or the source code has been stolen, or something along those lines as well. In some way, shape, or form, that code got into the hands of another threat actor group that is fluent in Korean,\u201d says Samani.<\/p>\n<p class=\"paywall\">An intriguing possibility, and also hard to pin down. Similarly, the \u201cfalse flag\u201d option\u2014that a hacking group wants to create cover by making it look like China is responsible\u2014isn\u2019t without precedent, but there are easier ways to mask your activities.<\/p>\n<p class=\"paywall\">\u201cThe place we do see a lot of this, a lot of espionage groups use open source or publicly available tools,\u201d says FireEye\u2019s Read. \u201cIt means you don\u2019t have to develop custom stuff, and it\u2019s harder to link things based on malware. It can obfuscate what\u2019s behind it, without implying it\u2019s someone else specifically.\u201d<\/p>\n<p class=\"paywall\">That there are no good answers around Oceansalt only adds to the intrigue. In the meantime, potential targets should be aware that a long-abandoned malware appears to have returned, creating brand new problems for its victims.<\/p>\n<p class=\"related-cne-video-component__dek\">Google CEO Sundar Pichai spoke with WIRED\u2019s Steven Levy as part of WIRED25, WIRED\u2019s 25th anniversary celebration in San Francisco.<\/p>\n<p><a href=\"https:\/\/www.wired.com\/story\/mysterious-return-of-years-old-chinese-malware-apt1\" target=\"bwo\" >https:\/\/www.wired.com\/category\/security\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5bc7cbce4bb3fa2ced830b1d\/master\/pass\/chinese_malware_v2.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Thu, 18 Oct 2018 04:01:00 +0000<\/strong><\/p>\n<p>Security researchers have discovered a new instance code associated with APT1, a notorious Chinese hacking group that disappeared in 2013.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10378,10607],"tags":[714],"class_list":["post-13624","post","type-post","status-publish","format-standard","hentry","category-security","category-wired","tag-security"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/13624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=13624"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/13624\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=13624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=13624"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=13624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}