RANSOM_DGER.THFAEAH
Artemis!688FD04F49B5 (McAfee), TR/ShadowBrokers.lpmcr (Avira)
Windows
Threat Type: Ransomware
Destructiveness: No
Encrypted: Yes
In the wild: Yes
OVERVIEW
Dropped by other malware
This Ransomware arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.
It drops files as ransom note.
TECHNICAL DETAILS
2,545,664 bytes
EXE
No
15 Jun 2018
Encrypts files, Connects to URLs/IPs, Displays message/message boxes
Arrival Details
This Ransomware arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.
Installation
This Ransomware drops the following files:
- %Program Data%\blue.exe - detected as TROJ_EQUATED.LZCMT
- %Program Data%\blue.fb
- %Program Data%\blue.xml
- %Program Data%\cnli-1.dll
- %Program Data%\coli-0.dll
- %Program Data%\crli-0.dll
- %Program Data%\dmgd-4.dll
- %Program Data%\down64.dll
- %Program Data%\exma-1.dll
- %Program Data%\libeay32.dll
- %Program Data%\libxml2.dll
- %Program Data%\posh-0.dll
- %Program Data%\ssleay32.dll
- %Program Data%\star.exe - detected as BKDR_EQUATED.LZCMU
- %Program Data%\star.fb
- %Program Data%\star.xml
- %Program Data%\tibe-2.dll
- %Program Data%\trch-1.dll
- %Program Data%\trfo-2.dll
- %Program Data%\tucl-1.dll
- %Program Data%\ucl.dll
- %Program Data%\xdvl-0.dll
- %Program Data%\zlib1.dll
- %Program Data%\uname.tmp
- %Program Data%\upass.tmp
- %System Root%\Users\All Users\uname
- %System Root%\Users\All Users\upass
- %Temp%\KSession
It drops and executes the following files:
- %Program Data%\mmkt.exe - detected as TROJ_GEN.R002C0OE518
- %System Root%\Satan.exe - detected as Ransom_NATAS.THFAEAH
(Note: %System Root% is the Windows root folder, where it usually is C:\ on all Windows operating system versions.)
It adds the following mutexes to ensure that only one of its copies runs at any one time:
- SATAN_SCAN_APP
- SATANAPP
Other Details
This Ransomware connects to the following URL(s) to check for an Internet connection:
- http://{BLOCKED}.{BLOCKED}.84.136
- http://{BLOCKED}.{BLOCKED}.64.9
- http://{BLOCKED}.{BLOCKED}.64.8
- http://{BLOCKED}.{BLOCKED}.64.70
- http://{BLOCKED}.{BLOCKED}.64.7
- http://{BLOCKED}.{BLOCKED}.64.69
- http://{BLOCKED}.{BLOCKED}.64.68
- http://{BLOCKED}.{BLOCKED}.64.67
- http://{BLOCKED}.{BLOCKED}.64.66
- http://{BLOCKED}.{BLOCKED}.64.65
- http://{BLOCKED}.{BLOCKED}.64.64
- http://{BLOCKED}.{BLOCKED}.64.63
- http://{BLOCKED}.{BLOCKED}.64.62
- http://{BLOCKED}.{BLOCKED}.64.61
- http://{BLOCKED}.{BLOCKED}.64.60
- http://{BLOCKED}.{BLOCKED}.64.6
- http://{BLOCKED}.{BLOCKED}.64.59
- http://{BLOCKED}.{BLOCKED}.64.58
- http://{BLOCKED}.{BLOCKED}.64.57
- http://{BLOCKED}.{BLOCKED}.64.56
- http://{BLOCKED}.{BLOCKED}.64.55
- http://{BLOCKED}.{BLOCKED}.64.54
- http://{BLOCKED}.{BLOCKED}.64.53
- http://{BLOCKED}.{BLOCKED}.64.52
- http://{BLOCKED}.{BLOCKED}.64.51
- http://{BLOCKED}.{BLOCKED}.64.50
- http://{BLOCKED}.{BLOCKED}.64.5
- http://{BLOCKED}.{BLOCKED}.64.49
- http://{BLOCKED}.{BLOCKED}.64.48
- http://{BLOCKED}.{BLOCKED}.64.47
- http://{BLOCKED}.{BLOCKED}.64.46
- http://{BLOCKED}.{BLOCKED}.64.45
- http://{BLOCKED}.{BLOCKED}.64.44
- http://{BLOCKED}.{BLOCKED}.64.43
- http://{BLOCKED}.{BLOCKED}.64.42
- http://{BLOCKED}.{BLOCKED}.64.41
- http://{BLOCKED}.{BLOCKED}.64.40
- http://{BLOCKED}.{BLOCKED}.64.4
- http://{BLOCKED}.{BLOCKED}.64.39
- http://{BLOCKED}.{BLOCKED}.64.38
- http://{BLOCKED}.{BLOCKED}.64.37
- http://{BLOCKED}.{BLOCKED}.64.36
- http://{BLOCKED}.{BLOCKED}.64.35
- http://{BLOCKED}.{BLOCKED}.64.34
- http://{BLOCKED}.{BLOCKED}.64.33
- http://{BLOCKED}.{BLOCKED}.64.32
- http://{BLOCKED}.{BLOCKED}.64.31
- http://{BLOCKED}.{BLOCKED}.64.30
- http://{BLOCKED}.{BLOCKED}.64.3
- http://{BLOCKED}.{BLOCKED}.64.29
- http://{BLOCKED}.{BLOCKED}.64.28
- http://{BLOCKED}.{BLOCKED}.64.27
- http://{BLOCKED}.{BLOCKED}.64.26
- http://{BLOCKED}.{BLOCKED}.64.25
- http://{BLOCKED}.{BLOCKED}.64.24
- http://{BLOCKED}.{BLOCKED}.64.23
- http://{BLOCKED}.{BLOCKED}.64.22
- http://{BLOCKED}.{BLOCKED}.64.21
- http://{BLOCKED}.{BLOCKED}.64.20
- http://{BLOCKED}.{BLOCKED}.64.2
- http://{BLOCKED}.{BLOCKED}.64.19
- http://{BLOCKED}.{BLOCKED}.64.18
- http://{BLOCKED}.{BLOCKED}.64.17
- http://{BLOCKED}.{BLOCKED}.64.16
- http://{BLOCKED}.{BLOCKED}.64.15
- http://{BLOCKED}.{BLOCKED}.64.14
- http://{BLOCKED}.{BLOCKED}.64.13
- http://{BLOCKED}.{BLOCKED}.64.12
- http://{BLOCKED}.{BLOCKED}.64.11
- http://{BLOCKED}.{BLOCKED}.64.10
- http://{BLOCKED}.{BLOCKED}.64.1
- http://{BLOCKED}.{BLOCKED}.64.0
Ransomware Routine
This Ransomware avoids encrypting files with the following strings in their file name:
- boot.ini
- bootmgr
- blue.exe
- cnli-1.dll
- coli-0.dll
- crli-0.dll
- dmgd-4.dll
- down64.dll
- exma-1.dll
- libeay32.dll
- libxml2.dll
- posh-0.dll
- ssleay32.dll
- star.exe
- tibe-2.dll
- trch-1.dll
- trfo-2.dll
- tucl-1.dll
- ucl.dll
- xdvl-0.dll
- zlib1.dll
- mmkt.exe
- Satan.exe
- {Malware filename}.exe
It renames encrypted files using the following names:
- [satan_pro@{BLOCKED}l.ru]{Filename}.satan
It drops the following file(s) as ransom note:
- {Drive Letter}:\_How_to_decrypt_files.txt
SOLUTION
9.850
14.314.10
15 Jun 2018
14.315.00
16 Jun 2018
Step 1
Before doing any scans, Windows XP, Windows Vista, and Windows 7 users must disable System Restore to allow full scanning of their computers.
Step 2
Note that not all files, folders, and registry keys and entries are installed on your computer during this malware's/spyware's/grayware's execution. This may be due to incomplete installation or other operating system conditions. If you do not find the same files/folders/registry information, please proceed to the next step.
Step 3
Identify and terminate files detected as RANSOM_DGER.THFAEAH
- Windows Task Manager may not display all running processes. In this case, please use a third-party process viewer, preferably Process Explorer, to terminate the malware/grayware/spyware file. You may download the said tool here.
- If the detected file is displayed in either Windows Task Manager or Process Explorer but you cannot delete it, restart your computer in safe mode. To do this, refer to this link for the complete steps.
- If the detected file is not displayed in either Windows Task Manager or Process Explorer, continue doing the next steps.
Step 4
Search and delete this file
- %Program Data%\blue.exe
- %Program Data%\blue.fb
- %Program Data%\blue.xml
- %Program Data%\cnli-1.dll
- %Program Data%\coli-0.dll
- %Program Data%\crli-0.dll
- %Program Data%\dmgd-4.dll
- %Program Data%\down64.dll
- %Program Data%\exma-1.dll
- %Program Data%\libeay32.dll
- %Program Data%\libxml2.dll
- %Program Data%\posh-0.dll
- %Program Data%\ssleay32.dll
- %Program Data%\star.exe
- %Program Data%\star.fb
- %Program Data%\star.xml
- %Program Data%\tibe-2.dll
- %Program Data%\trch-1.dll
- %Program Data%\trfo-2.dll
- %Program Data%\tucl-1.dll
- %Program Data%\ucl.dll
- %Program Data%\xdvl-0.dll
- %Program Data%\zlib1.dll
- %Program Data%\mmkt.exe
- %Program Data%\uname.tmp
- %Program Data%\upass.tmp
- %System Root%\Users\All Users\uname
- %System Root%\Users\All Users\upass
- %System Root%\Satan.exe
Step 5
Scan your computer with your Trend Micro product to delete files detected as RANSOM_DGER.THFAEAH. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check the following Trend Micro Support pages for more information:
Step 6
Restore encrypted files from backup.
Did this description help? Tell us how we did.