{"id":86560,"date":"2018-07-25T19:10:33","date_gmt":"2018-07-25T13:40:33","guid":{"rendered":"https:\/\/blogs_admin.quickheal.com\/?p=86560"},"modified":"2018-07-25T19:10:33","modified_gmt":"2018-07-25T13:40:33","slug":"evolution-4-year-old-threat-emotet-infamous-trojan-complex-threat-distributer","status":"publish","type":"post","link":"https:\/\/www.quickheal.com\/blogs\/evolution-4-year-old-threat-emotet-infamous-trojan-complex-threat-distributer\/","title":{"rendered":"The evolution of a 4-year-old-threat Emotet: From an infamous Trojan to a complex threat distributer"},"content":{"rendered":"

Emotet malware campaign has been existing for a long time. It comes frequently in intervals with different techniques and variants to deliver malware on a victim. Attackers are smart and they use complex techniques to avoid detection. At the start of 2017, we had seen the emotet campaign spreading through email attached PDF and JS file. This time, it is spreading through MS Office Word documents with a heavily obfuscated macro inside it.<\/p>\n

Attack chain<\/b><\/strong><\/p>\n

\"Attack
Fig.1 Attack Chain<\/figcaption><\/figure>\n

The spreading mechanism of this campaign is a phishing email. It uses subject lines like \u2018Invoice\u2019, \u2018Delivery details\u2019, \u2018Shipment details\u2019, \u2018Payment details\u2019 and so on to trick the victim into opening the email. Such emails have compromise or phishing sites that will download a Word document. Another way is directly attaching a document inside the email or sometimes attaching a compressed file having a document file.<\/p>\n

\"\"
Fig.2 Phishing Mail<\/figcaption><\/figure>\n

 <\/p>\n

Detail analysis of Macro<\/b><\/strong><\/p>\n

A malicious office document embedded with macro, on clicking on Enable Editing a macro code will be activated. We have taken one sample. it’s having two heavily obfuscated macros inside, such as “prMzoHTQ” & “zdXXRhCd”, a code has Sub AutoOpen() function is executing the macros.<\/p>\n

\"\"
Fig.3 Macro Workflow<\/figcaption><\/figure>\n

In first macro “zdXXRhCd” one function FAUzvR() which accepts a string as an argument. In the phase of deobfuscation, we found that there were used junk code to do complications in reverse the code, On Error Resume Next, it means there is junk code if it exists ignore it. Shell is using to execute the code, next to the shell there is vbkeyP which means the letter “P”. Values MIqCuXCZPMl, SOznt, and 4 others are parameters are passed to function FAUzvR() as shown in the figure, These are declared as a function in the second macro. The motivation of the second macro is combining strings and return a value to functions FAUzvR() to the first macro. function FAUzvR() create a WScript Shell object, execute the functions with vbkeyP in order to get below output.
\n“PowersHeLL -e KABuAEUAVwAtAG8AYgBKAEUAYwBUACAAIABT……”<\/p>\n

We get final PowerShell command as shown in below figure.<\/p>\n

\"\"
Fig.4 PowerShell command<\/figcaption><\/figure>\n

While looking at command, we found that PowerShell with encoded base64 string. After decoding the base64 string, we get below output-<\/p>\n

\"Fig.5
Fig.5 After base64 decode.<\/figcaption><\/figure>\n

Then it is showing a Powershell script. Its contents compressed Base64 string with Powershell parameters. Here in script use IO.StreamReader initializes a new instance of StreamReader class for the specified file, with specified character encoding. IO.compression.compressionMode is set the compression mode to Decompression. Deflate stream object will be stream decompressed bytes from MemoryStream. [SySTem.tExt.encodIng]::ASCII It set to ASCII encoding. REadtOEND() reads the entire stream and returns the ASCII string contained in it.<\/p>\n

For deobfuscation of the script we need to first decode the string with base64, then us decompression will get output in below figure-<\/p>\n

\"\"
Fig.6 De-obfuscation Powershell stage2<\/figcaption><\/figure>\n

We finally get a deobfuscated script. It has a list of malicious URLs. The script downloads malware from URLs and generates random file names by picking in bet 1 to 994915, then kept at %temp% location as a .exe extension. Then the malware will be executed using Start-Process.<\/p>\n

We have come across with different obfuscation ways as shown in below figures.<\/p>\n

\"\"
Fig.7 Obfuscated pattern1<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Fig.8 Obfuscated pattern2<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Fig.9 Obfuscated pattern3<\/figcaption><\/figure>\n

 <\/p>\n

Payload Analysis<\/b><\/strong><\/p>\n

The downloaded payload “{Random_number}.exe<\/i><\/em>” is then executed from %temp% location.<\/p>\n

In this case, we found the payload name as “iwamregutilman.exe”<\/i><\/em>. This rename its instance and launched its copy of name “wsdquota.exe” <\/i><\/em>from “C:\\Windows\\system32” location.<\/p>\n

This file again spawned a new instance of its own and show its activity.<\/p>\n

\"\"
Fig.10 The execution flow<\/figcaption><\/figure>\n

The downloaded payload has a pre-defined list of words, by using a combination of 2 words from this list it creates the name of 2nd<\/sup>\u00a0self-copy executes from respective locations. If the system is 32-bit, then it executed its self-copy from “C:\\Windows\\System32” folder else if it is 64-bit then the location is “C:\\Windows\\SysWOW64”.<\/p>\n

\"\"
Fig.11 List of file names<\/figcaption><\/figure>\n

The following is the list of names stored in this file.<\/p>\n

\"Fig.12
Fig.12 Total list of names<\/figcaption><\/figure>\n

By combining the 1st<\/sup>\u00a0word as “wsd” and 2nd<\/sup>\u00a0word is “quota” it creates the name of the file name as “wsdquota.exe”.<\/p>\n

The first instance of the dropped file contains the huge encrypted data. This data will get decrypted at runtime and writes 2 another PE file in memory which can be used by the parent file for further process.<\/p>\n

After this, the parent process checks whether the process is spawned by itself or not. If not, then it creates one mutex and closes the parent process and run as an individual.<\/p>\n

The spawned process will list out all the running process and stores it in a memory. After that, it starts enumerating each process.<\/p>\n

\"\"
Fig.13 Show each process list enumeration<\/figcaption><\/figure>\n

By using the CreateToolhelp32Snapshot<\/u><\/a>\u00a0function, it takes the snapshot of each process and threads, heaps and modules used by these processes.<\/p>\n

\"\"
Fig.14 Use of CreateToolhelp32Snapshot function<\/figcaption><\/figure>\n

After taking the details of each running process, malware starts to encrypting the data and sends to the malicious server in POST request.<\/p>\n

\"\"
Fig.15 Post request<\/figcaption><\/figure>\n

As the all malicious servers are not active, so we can’t find the post activity after the response of this malware.<\/p>\n

Following is the list of malicious URLs present in malware which sends the POST request to each URL.<\/p>\n

\"\"
Fig.16 CnC request domain list<\/figcaption><\/figure>\n

IOCs<\/b><\/strong><\/p>\n

4154619d2075d3f6c9e73bf4cdccdb17 (DOC)<\/p>\n

6f86fa7d95fed4472ad03eb77cb6a9a4 (DOC)<\/p>\n

2dcf064d40ef8fda90193fb00d306020 (DOC)<\/p>\n

8249D414627D3DDE168318C92A63F74A (PE)<\/p>\n

7B6E1369FF14E16A4815AE1DB32F0794 (PE)<\/p>\n

\u00a0<\/b><\/strong><\/p>\n

Detection Statistics<\/b><\/strong><\/p>\n

Quick heal has successfully detected the spam email which is the initial vector of the Emotet campaign. It is a special type of a detection provided by Quick Heal for detecting such kinds of campaigns.<\/p>\n

Below are the last one-month statistics of email detections.<\/p>\n

\"\"
Fig.17 Email detections<\/figcaption><\/figure>\n

As Quick Heal is detecting the initial vector of Emotet campaign, we have seen less hits from the second and third vector of this campaign.<\/p>\n

\"\"
Fig.18 Doc and Executable detections<\/figcaption><\/figure>\n

\u00a0<\/b><\/strong><\/p>\n

Detection Names<\/b><\/strong><\/p>\n

    \n
  • MIME.Emotet.Downloader.31464<\/li>\n
  • MIME.Emotet.31831<\/li>\n
  • MIME.Emotet.31617<\/li>\n
  • MIME.Emotet.31618<\/li>\n
  • W97M.Emotet.31645<\/li>\n
  • W97M.Emotet.31769<\/li>\n
  • X97M.Emotet.32092<\/li>\n
  • Trojan.Emotet.Y4<\/li>\n
  • Trojan.Emotet.X4<\/li>\n<\/ul>\n

    Conclusion<\/b><\/strong><\/p>\n

    Spreading Emotet malware via spam mail which has social engineering tricks to phish the user easily.<\/p>\n

    Quick Heal provides multilayered protection against each layer of Emotet campaign.<\/p>\n

    Security measures to follow<\/b><\/strong><\/p>\n

      \n
    • Don’t open any link in mail body sent by an unknown source.<\/li>\n
    • Don’t download attachments received by an untrusted source.<\/li>\n
    • Always turn on email protection of your antivirus software.<\/li>\n
    • Don’t enable \u2018macros\u2019 or ‘editing mode’ upon execution of the document.<\/li>\n<\/ul>\n

       <\/p>\n

      Subject Matter Experts:<\/b><\/strong><\/p>\n

      Prashant Tilekar, Aniruddha Dolas, Preksha Saxena, Prakash Galande, Vallabh Chole | Quick Heal Security Labs<\/p>\n","protected":false},"excerpt":{"rendered":"

      Emotet malware campaign has been existing for a long time. It comes frequently in intervals with different techniques and variants to deliver malware on a victim. Attackers are smart and they use complex techniques to avoid detection. At the start of 2017, we had seen the emotet campaign spreading through email attached PDF and JS […]<\/p>\n","protected":false},"author":38,"featured_media":86561,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21,24,303,5,293],"tags":[1443,1615,1503,1548,521],"class_list":["post-86560","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email","category-malware","category-phishing","category-security","category-spam","tag-banking-malware","tag-emotet","tag-malspam","tag-obfuscation","tag-phishing-email"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/posts\/86560"}],"collection":[{"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/users\/38"}],"replies":[{"embeddable":true,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/comments?post=86560"}],"version-history":[{"count":1,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/posts\/86560\/revisions"}],"predecessor-version":[{"id":86562,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/posts\/86560\/revisions\/86562"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/media\/86561"}],"wp:attachment":[{"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/media?parent=86560"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/categories?post=86560"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.quickheal.com\/blogs\/wp-json\/wp\/v2\/tags?post=86560"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}