Ransom.Win32.STOP.CL
Trojan:Win32/Mokes.PVD!MTB, Ransom.Stop
Windows

Threat Type: Ransomware
Destructiveness: No
Encrypted:
In the wild: Yes
OVERVIEW
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 uses the Windows Task Scheduler to add a scheduled task that executes the copies it drops.
As of this writing, the said sites are inaccessible.
It drops files as ransom note. It avoids encrypting files with the following file extensions.
TECHNICAL DETAILS
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 copies of itself into the affected system:
- %AppDataLocal%\{GUID}\{malware filename}
(Note: %AppDataLocal% is the Local Application Data folder, which is usually C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000(32-bit), XP, and Server 2003(32-bit), or C:\Users\{user name}\AppData\Local on Windows Vista, 7, 8, 8.1, 2008(64-bit), 2012(64-bit) and 10(64-bit).)
It drops the following files:
- %System Root%\SystemID\PersonalID.txt
- %AppDataLocal%\{GUID}\{downloaded file}
- {folder of encrypted files}\_readme.txt
- %AppDataLocal%\bowsakkdestx.txt
- %TEMP%\delself.bat (deleted afterwards)
(Note: %System Root% is the Windows root folder, where it usually is C:\ on all Windows operating system versions.. %AppDataLocal% is the Local Application Data folder, which is usually C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000(32-bit), XP, and Server 2003(32-bit), or C:\Users\{user name}\AppData\Local on Windows Vista, 7, 8, 8.1, 2008(64-bit), 2012(64-bit) and 10(64-bit).)
It uses the Windows Task Scheduler to add a scheduled task that executes the copies it drops.
It adds the following processes:
- icacls "%AppDataLocal%\{GUID}" /deny *S-1-1-0:(OI)(CI)(DE,DC)
- "{malware Path}\{malware filename}.exe" --Admin IsNotAutoStart IsNotTask (*if not run as admin)
(Note: %AppDataLocal% is the Local Application Data folder, which is usually C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000(32-bit), XP, and Server 2003(32-bit), or C:\Users\{user name}\AppData\Local on Windows Vista, 7, 8, 8.1, 2008(64-bit), 2012(64-bit) and 10(64-bit).)
It creates the following folders:
- %AppDataLocal%\{GUID}\
- %System Root%\SystemID\
(Note: %AppDataLocal% is the Local Application Data folder, which is usually C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000(32-bit), XP, and Server 2003(32-bit), or C:\Users\{user name}\AppData\Local on Windows Vista, 7, 8, 8.1, 2008(64-bit), 2012(64-bit) and 10(64-bit).. %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:
- {FBB4BCC6-05C7-4ADD-B67B-A98A697323C1}
- {1D6FC66E-D1F3-422C-8A53-C0BBCF3D900D}
Autostart Technique
This Ransomware adds the following registry entries to enable its automatic execution at every system startup:
HKCU\Software\Microsoft\
Windows\CurrentVersion\Run
SysHelper = %AppDataLocal%\{GUID}\{malware filename} --AutoStart
Other System Modifications
This Ransomware adds the following registry entries as part of its installation routine:
HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion
SysHelper = 0 or 1
Process Termination
This Ransomware terminates processes or services that contain any of the following strings if found running in the affected system's memory:
- MYSQL
Download Routine
This Ransomware connects to the following website(s) to download and execute a malicious file:
- http://{BLOCKED}d.top/files/penelop/updatewin1.exe
- http://{BLOCKED}d.top/files/penelop/updatewin2.exe
- http://{BLOCKED}d.top/files/penelop/updatewin.exe
- http://{BLOCKED}d.top/files/penelop/3.exe
- http://{BLOCKED}d.top/files/penelop/4.exe
- http://{BLOCKED}d.top/files/penelop/5.exe
It connects to the following URL(s) to download its component file(s):
- http://{BLOCKED}d.top/ydtftysdtyftysdfsdpen3/get.php?pid={MD5 of MAC address}&first={True/False}
As of this writing, the said sites are inaccessible.
Information Theft
This Ransomware gathers the following data:
- MD5 of MAC address (used for identification purposes)
Other Details
This Ransomware connects to the following URL(s) to get the affected system's IP address:
- https://api.2ip.ua/geo.json
It does the following:
- It terminates and deletes itself on the affected system if the return of the IP address location is any of the following:
- RU (Russia)
- BY (Belarus)
- UA (Ukraine)
- AZ (Azerbaijan)
- AM (Armenia)
- TJ (Tajikistan)
- KZ (Kazakhstan)
- KG (Kyrgyzstan)
- UZ (Uzbekistan)
- SY (Syrian Arab Republic)
It accepts the following parameters:
- --Admin
- --AutoStart
- --ForNetRes
- --Service
- IsAutoStart
- IsNotAutoStart
- IsTask
- IsNotTask
It adds the following scheduled tasks:
- Task Name: Time Trigger Task
- Trigger: One time; Once triggered, repeats every 5 minutes
- Task to run: %AppDataLocal%\{GUID}\{malware filename} --Task
(Note: %AppDataLocal% is the Local Application Data folder, which is usually C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000(32-bit), XP, and Server 2003(32-bit), or C:\Users\{user name}\AppData\Local on Windows Vista, 7, 8, 8.1, 2008(64-bit), 2012(64-bit) and 10(64-bit).)
Ransomware Routine
This Ransomware avoids encrypting files with the following strings in their file name:
- ntuser.dat
- ntuser.dat.LOG1
- ntuser.dat.LOG2
- ntuser.pol
It avoids encrypting files found in the following folders:
- {Drive}:\SystemID\
- {Drive}:\Users\Default User\
- {Drive}:\Users\Public\
- {Drive}:\Users\All Users\
- {Drive}:\Users\Default\
- {Drive}:\Documents and Settings\
- {Drive}:\ProgramData\
- {Drive}:\Recovery\
- {Drive}:\System Volume Information\
- {Drive}:\Users\%username%\AppData\Roaming\
- {Drive}:\Users\%username%\AppData\Local\
- {Drive}:\Windows\
- {Drive}:\PerfLogs\
- {Drive}:\ProgramData\Microsoft\
- {Drive}:\ProgramData\Package Cache\
- {Drive}:\Users\Public\
- {Drive}:\$Recycle.Bin\
- {Drive}:\$WINDOWS.~BT\
- {Drive}:\dell\
- {Drive}:\Intel\
- {Drive}:\MSOCache\
- {Drive}:\Program Files\
- {Drive}:\Program Files (x86)\
- {Drive}:\Games\
- {Drive}:\Windows.old\
It appends the following extension to the file name of the encrypted files:
- .mpaj
It drops the following file(s) as ransom note:
- {directory of encrypted files}\_readme.txt
It avoids encrypting files with the following file extensions:
- .sys
- .ini
- .DLL
- .dll
- .blf
- .bat
- .lnk
- .regtrans-ms
SOLUTION
Step 1
Trend Micro Predictive Machine Learning detects and blocks malware at the first sign of its existence, before it executes on your system. When enabled, your Trend Micro product detects this malware under the following machine learning name:
-
Troj.Win32.TRX.XXPE50FFF034
Step 2
Before doing any scans, Windows 7, Windows 8, Windows 8.1, and Windows 10 users must disable System Restore to allow full scanning of their computers.
Step 3
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 4
Identify and terminate files detected as Ransom.Win32.STOP.CL
- 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 5
Delete this registry value
Important: Editing the Windows Registry incorrectly can lead to irreversible system malfunction. Please do this step only if you know how or you can ask assistance from your system administrator. Else, check this Microsoft article first before modifying your computer's registry.
- In HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
- SysHelper = %AppDataLocal%\{GUID}\{malware filename} --AutoStart
- SysHelper = %AppDataLocal%\{GUID}\{malware filename} --AutoStart
- In HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
- SysHelper = 0 or 1
- SysHelper = 0 or 1
Step 6
Deleting Scheduled Tasks
The following {Task Name} - {Task to be run} listed should be used in the steps identified below:
- Task Name: Time Trigger Task
- Task to run: %AppDataLocal%\{GUID}\{malware filename} --Task
For Windows 2000, Windows XP, and Windows Server 2003:
- Open the Windows Scheduled Tasks. Click Start>Programs>Accessories>
System Tools>Scheduled Tasks. - Locate each {Task Name} values listed above in the Name column.
- Right-click on the said file(s) with the aforementioned value.
- Click on Properties. In the Run field, check for the listed {Task to be run}.
- If the strings match the list above, delete the task.
For Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows 8.1, and Windows Server 2012:
- Open the Windows Task Scheduler. To do this:
• On Windows Vista, Windows 7, and Windows Server 2008, click Start, type taskschd.msc in the Search input field, then press Enter.
• On Windows 8, Windows 8.1, and Windows Server 2012, right-click on the lower left corner of the screen, click Run, type taskschd.msc, then press Enter. - In the left panel, click Task Scheduler Library.
- In the upper-middle panel, locate each {Task Name} values listed above in the Name column.
- In the lower-middle panel, click the Actions tab. In the Details column, check for the {Task to be run} string.
- If the said string is found, delete the task.
Step 7
Search and delete these files
- %System Root%\SystemID\PersonalID.txt
- %AppDataLocal%\{GUID}\{malware filename}
- {folder of encrypted files}\_readme.txt
- %AppDataLocal%\bowsakkdestx.txt
Step 8
Search and delete these folders
- %System Root%\SystemID\
- %AppDataLocal%\{GUID}\
Step 9
Scan your computer with your Trend Micro product to delete files detected as Ransom.Win32.STOP.CL. 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 10
Restore encrypted files from backup.
Did this description help? Tell us how we did.