- Cisco Talos has observed a new version of a remote access trojan (RAT) family known as CRAT.
- Apart from the prebuilt RAT capabilities, the malware can download and deploy additional malicious plugins on the infected endpoint.
- One of the plugins is a ransomware known as "Hansom."
- CRAT has been attributed to the Lazarus APT Group in the past.
- The RAT consists of multiple obfuscation techniques to hide strings, API names, command and control (C2) URLs and instrumental functions, along with static detection evasion.
- The attack also employs a multitude of anti-infection checks to evade sandbox based detection systems.
Cisco Talos has recently discovered a new version of the CRAT malware family. This version consists of multiple RAT capabilities, additional plugins and a variety of detection-evasion techniques. In the past, CRAT has been attributed to the Lazarus Group, the malicious threat actors behind multiple cyber campaigns, including attacks against the entertainment sector.
Indicators and tactics, techniques and procedures (TTPs) discovered by this investigation resemble those of the Lazarus Group.
How did it work?
The attack consists of a highly modular malware that can function as a standalone RAT and download and activate additional malicious plugins from its C2 servers. Cisco Talos has discovered multiple plugins so far, consisting of ransomware, screen-capture, clipboard monitoring and keylogger components.
This attack demonstrates how the adversary operates an attack that:
- Uses obfuscation and extensive evasion techniques to hide its malicious indicators.
- Has evolved across versions to achieve effectiveness of their attack.
- Employs a highly modular plugin framework to selectively infect targeted endpoints.
- Most importantly, it deploys RAT malware to ransack the endpoint, followed by deployment of ransomware to either extort money or burn infrastructure of targeted entities.
The first version of CRAT has been known to be distributed via malicious HWPs. The HWPs masquerade as a COVID-19 themed document pertaining to an infectious disease management support group from South Korea. The HWPs consisted of an exploit for CVE-2017-8291 used to activate malicious shellcode. The shellcode would then download and execute CRATv1 on the infected endpoint.
The distribution vector of the new version of CRAT (v2) is currently unknown. However, it is highly likely the attackers may have re-used a maldoc-based infection vector to spread CRATv2 as well.
Malicious HWP document - downloader for CRATv1
Shellcode executing PowerShell to download and activate CRATv1 via regsvr32.
Before we analyze the attack it is important to understand the extensive measures taken by the attackers to conceal the RAT executables. The RAT is highly obfuscated in terms of:
- String Obfuscation: Almost all of the strings are obfuscated using a four-byte XOR key and subsequent base64 encoding. String obfuscations are used to thwart string-based static malware detection signatures.
- API Resolution: All APIs used are resolved dynamically. The process of selecting the API to call is also a cumbersome algorithm (overkill) involving index tables, switch cases and API name deobfuscation. This technique is used to make analysis cumbersome for an analyst by hiding API call sequences.
- Runtime Code Patching: The malware consists of a select few instrumental subroutines that are decoded, executed and then patched/encoded again (during runtime). On-the-fly patching of subroutines/functions may be aimed towards evading detection mechanisms that scan process memory to identify malicious strings and code.
WHY THE OCCURRENCE OF MULTIPLE OBFUSCATIONS?
The use of multiple obfuscations signifies the attackers confidence in selective obfuscation rather than the use of packers as a means of evasion. Many detection systems look for the presence of a packer using techniques such as entropy analysis, Import API analyses, etc. Selective obfuscation of code and strings prevents these systems from detecting the malware solely on the basis of the obfuscations.
It is also likely that this group of attackers employs a modular build system that obfuscates different aspects of malware. Different modules can thus be used in conjunction to produce a combination of obfuscations for the same malware.
MASQUERADING AS LEGITIMATE
The attackers have also used file names and export API names in the CRAT DLLs to masquerade the RAT as a benign application's library. Some examples of the exported function names are:
The implant performs checks to verify its execution on an allowed endpoint. The implant uses a variety of criteria to identify a blocklisted system by utilizing:
- Process name blocklists
- Network adapter name blocklists
- MAC Address blocklists
- Analysis tool names blocklists
The implant also checks for indicators that the process is being debugged (including CheckRemoteDebuggerPresent). If the infected endpoint fails any of the anti-infection checks, the implant quits execution. The blocklists are provided at the end of this post.
Finding the right process — Sweet Home Alabama
The CRAT DLL ensures it resides in the desired process on the infected endpoint. Depending on the MS Windows OS version, it will inject and reflectively-load itself into the right process. The processes trojanized by CRAT v2 are:
Other Win 6.x:
OS agnostic injection fall back process: explorer.exe
Before detailing CRAT's capabilities, it is important to illustrate the communication mechanism used by CRAT to talk to its C2 servers.
Both versions of CRAT use HTTP to communicate with the C2 servers. The data sent to the C2 is in the form of URL-encoded form data and may consist of 3 types of requests:
- Login: Login/check-in with the C2 to register the infected endpoint.
- Question: Request a command code to execute a malicious RAT functionality on the endpoint.
- Answer: Respond to the C2's command with the output of the executed RAT functionality.
The HTTP GET/POST requests are sent to the C2 URLs appended with a 'timestamp' value: http(s)://<C2_url>?ts=<epoch_time>_<rand>
CRAT uses the following algorithm to encode the data before sending it out via the HTTP POST request:
- Generate a random four-byte value (DWORD).
- XOR the data to be exfiltrated with the DWORD.
- Base64-encode (std alphabet) the XOR key and the XORed data to achieve the final form of the data.
- Exfiltrate the encoded data as URL encoded form data.
The format of the response to the C2 is:
- code = type of the communication being done. Values include:
- login = login request to C2 from implant
- question = request command to be processed
- answer = response to command executed
- token = a token value sent by the C2 as a response to the login (session identifier)
- content = the actual base64-encoded + XORed data being exfiltrated
- frags = number of fragments of data being POSTed to the C2
- limit = retry count in case of failure to send
The C2 server will respond with a JSON containing command codes and supporting data to be recognized by the implant to execute a corresponding RAT capability.
The CRAT malware consists of multiple RAT capabilities that allow it to be highly versatile and dangerous. CRAT executes these capabilities by receiving command codes and corresponding data from the C2 in the form of JSONs communicated over HTTP.
Apart from the introduction of a wide variety of new RAT capabilities in CRAT version 2 (vs CRAT version 1), the biggest update is the spin-off of key RAT capabilities into plugin modules. These plugins (DLLs) are downloaded on-the-fly by CRATv2 and injected into specific processes running on the infected endpoint.
The following capabilities have been observed in CRATv2.
COLLECT SYSTEM INFORMATION
Collects the following system information:
- Installed AntiVirus software names
- Installed FirewallProduct names
- Domain Names:
- Netbios domain name
- DNS domain name
- Domain forest name
- File version number from DLLs embedded Version Information
- Path to the system folder
- Flag if the current user has administrative privileges
Implant checking for ADMIN privileges
- TCP/IP enabled MAC Addresses using WMI query:
wmic PATH Win32_NetworkAdapterConfiguration WHERE IPEnabled=TRUE GET MACAddress.
Implant replacing strings in the output of the WMIC command to obtain only the MAC Addresses
ENUMERATE DRIVES AND GATHER FILE SIZE INFORMATION
Collects size information about all files and folders on the infected endpoint except:
- Recycle Bin
The data gathered is arranged into a specific format:
<Drive_Letter>\t<Disk_Type>\r\n [DIR]\t<Folder_Path> \t<File_Name><spaces><size_in_bytes> bytes
Where Disk Type =
- Local Disk
- CD ROM
- Removable Disk
- Remote Disk
- RAM Disk
- Unknown Disk
Snippet of drive and file size information gathered by the implant.
ENUMERATE DRIVES USING DIR
Enumerate drives using the 'dir' command:
cmd /c "dir <drive_name> /s >> %temp%\<custom_prefix>error.log"
Where custom_prefix = file name prefix specified by the C2
E.g. cmd /c "dir C:\ /s >> C:\Users\<username>\AppData\Local\Temp\BLAHerror.log"
Implant constructing the dir cmd to be executed.
The log file is then rolled up into a ".rar" archive using a pre-existing installation of a RAR archiver program using the command:
<rar_utility> a -k -r -s -ibck -m5 <output_rar_filepath> <input_log_filepath>
The RAR archive is then read to memory and exfiltrated to the C2, followed by deletion of the .rar and log files.
READ AND WRITE FILE
CRAT has the capability to read the contents of the file specified by the C2 and exfiltrate these to the C2. The write file capability consists of writing the data received from the C2 to a temporary file in the %temp% folder: %temp%\<temp_name>.tmp
The implant will also timestomp the tmp file to either a hardcoded value or copy the filetimes from a system file such as %windir%\system32\user32.dll.
Execute commands with two variations of the functionality:
- Simply execute the command on the endpoint.
- Execute a command and send output of command to C2.
Open up a reverse command shell for arbitrary command execution using Windows pipes.
SET QUERY TIMES
This capability allows the C2 to specify delays between consecutive command queries from the implant to the C2 for:
- Receiving commands from the C2.
- Receiving arbitrary commands to execute in the reverse shell.
STEAL BROWSER PASSWORDS: CHROMEPASS
Execute chromepass.exe with the /stext switch to obtain the usernames and passwords stored in Google Chrome. The credentials are dumped to a text file which is read and exfiltrated to the C2.
Command format: chromepass.exe /stext <output_filepath>
CRAT contains a RAT functionality that implements a custom-built File Explorer sub-module.
The C2 specifies the parent functionality command code and an additional sub-command code to specify the sub-capability to be executed in the file explorer. The file explorer sub-module contains the following sub-capabilities:
- Gather free and total disk space information for each drive on the system.
- Enumerate file listings (recursively) in a given directory.
- Move files across locations.
- Find and remove files and folders.
- Create RAR archive files from files specified.
- Create RAR archives and exfiltrate file contents to C2.
- Execute arbitrary commands specified by C2 on the endpoint.
Downloads and installs a malicious plugin from the C2. The plugin is placed in a standard directory specified by the C2, and locations may include:
- %APPDATA% (%USERPROFILE%\AppData\Roaming)
CRAT can also administer the malicious plugins by performing the following actions:
- For EXE based plugins:
- Execute plugin as an independent process.
- For DLL plugins:
- Activate using regsvr32.exe
- Activate using rundll32.exe
- Reflective load into its own process
- Reflectively load into a target process
- Delete files related to plugins
The RAT comes with an uninstallation routine built into it as well. This routine can be triggered in response to a command issued by the C2 or if the endpoint fails its anti-infection checks. The uninstallation routine consists of:
- Deleting .exe and .lnk files associated with the RAT.
- Sending the uninstall flag to the communications pipe.
- Delete associated plugin files (EXEs and DLLs) from the endpoint.
In addition to the RAT capabilities, CRAT also consists of additional functionalities that are implemented as part of independent threads in the infected process:
- Send Heartbeat Thread: This will send four bytes of data periodically to a named pipe.
- Upload File Thread: This thread will periodically send the contents of a file to the C2 server over HTTP. The contents of either the Keylogger or Clipboard monitor files are read and sent to the C2.
- Upload Screen Thread: This thread reads and sends the contents of another file to the C2 server over HTTP. Most likely the content of screenshots taken by the Screen Recorder plugin.
With version 2, the attackers have evolved CRAT into a modular RAT with the ability to download and activate additional malicious plugins (DLLs) on the infected endpoint. The first version of CRAT had these plugin capabilities implemented within the RAT. Cisco Talos has discovered these capabilities so far:
- Screen capture plugins
- Clipboard monitor plugins
- Keylogger plugins
SCREEN CAPTURE PLUGIN
The screen capture plugin will capture the current foreground window (every second or so) and save the screenshot to a .tmp file in a hardcoded directory. The screenshot is saved in TIFF file format. Since TIFF is widely supported by scanning and faxing systems, the malicious screenshots may be mis-identified as document scans by a forensic analyst instead of malicious screen captures.
The saved screenshot file is also XORed using a variable length XOR key hardcoded into the plugin as saved to add a further layer of obfuscation.
Sample screenshot captured by the plugin
CLIPBOARD MONITOR PLUGIN
This plugin will read the clipboard data and write the contents of the clipboard to a log file. The format of the clipboard data logged is:
The data is stored in a seemingly benign file location such as: %localappdata%\Google\Chrome\Application\Update.chk
Clipboard monitor implant getting clipboard data.
The keylogger plugin monitors the state of all the alphanumeric keys pressed. It also logs the following keys:
- Function keys
The keystrokes are logged to another seemingly benign file on the endpoint such as:
The format of the log file is:
\r\n[<Window_Name> - YYYY-mm-DD HH:MM:SS]\r\n<keylogger_data>
[Untitled - Notepad - 2020-06-05 01:02:03]
These keystrokes are being recorded[ENTER]
[Blah - 2020-06-05 01:02:03]
[CTRL] + c
Keywords used to log keys being pressed.
Ransomware plugin — Hansom
We also discovered a ransomware plugin that encrypts specific file extensions on the infected endpoint. Traditionally ransomware encrypts files on the infected endpoint using a combination of asymmetric and symmetric encryption. This plugin is different.
It locks files into individually created archives using randomly generated passwords. The passwords are then encrypted using an embedded public key (part of an embedded pub certificate). Once the infected user gets access to the private key (after the ransom has been paid), the private key can be plugged into the accompanying decryptor .exe that decrypts the archive passwords and subsequently unpacks the original files from the archive.
The plugin performs the following housekeeping actions before it begins encrypting files on the endpoint:
- Terminate specific application processes.
- Suppress Windows Defender notifications by setting registry value: HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\UX Configuration | Notification_Suppress = 0x1
- Terminate Windows Defender process "MsMpEng.exe" specifically.
- Disable task manager via registry: HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System | DisableTaskMgr = 0x1
- Setup persistence for self via registry and regsvr32: HKCU\Software\Microsoft\Windows\CurrentVersion\Run | HANSOM = regsvr32.exe /s <filepath_to_ransomware_dll>
TARGETED FILE EXTENSIONS
The following file extensions are targeted by the ransomware plugin. The ransomware excludes certain file and folder names from encryption to ensure the stability of the Operating System (listed in the IOCs section).
RANSOMWARE ENCRYPTION ALGORITHM
The plugin uses the following sequence of steps to encrypt/lock files on the infected endpoint:
- Create a password by generating random 0x48 bytes and base64 encoding them. Then take the target file and add it to a password-protected RAR archive using command:
"C:\Users\<username>\AppData\Roaming\WinRar\Rar.exe" a -y -ep -k -r -s -ibck -df -m0 -hp<password> -ri1:250 "<target_filepath>.rar" "<target_filepath>"
This command also deletes the target file once it has been added to the archive.
- After the target file has been archived, the random password used for the creation of the RAR archive is encrypted using an embedded RSA public key.
- The encrypted password blob is appended to the archive along with a marker indicating that the file has been encrypted successfully. The marker used is:
48 61 6E 73 6F 6D 32 30 30 38 20 20 07 29 Hansom2008 .)
- Then the RAR archive is renamed (via file move) to the name of the original file.
E.g. C:\blah\abc.txt.rar is renamed back to C:\blah\abc.txt
- A ransom note is dropped in the target file's directory named HANSOM_README.txt informing the user of the ransomware infection.
The BTC addresses discovered so far do not hold any money (with no transactions made in or out of the BTC addresses).
The ransomware plugin performs the following activities after it has encrypted all the targeted files on the system:
- Create and encrypt sample files on desktop folder "Hansom_Sample" for demonstrating the decryptor:
- Drop the decryptor .exe to the current user's desktop as "Hansom Decryptor.exe".
- Copy the ransom note JPG to C:\Users\Public\Pictures\hansom.jpg and set it as the current wallpaper via registry.
Hansom ransomware wallpaper:
- Remove any registry based persistence mechanisms such as Run keys to prevent re-encryption of files on startup.
- Delete disk shadow copies using wmic command: shadowcopy delete
The ransomware plugin also communicates with a C2 server URL, sending it details (as JSONs) such as:
- Unique ID of machine (generated similar to CRAT)
- Ransom ID of the plugin
- Number of files encrypted
- Privilege level of the process, etc.
In addition to the CRATv2 DLLs, Cisco Talos discovered multiple loaders related to the RAT family. This section provides an overview of these components.
The EXE based loader serves two primary purposes:
- Establish persistence for itself using a scheduled task on the infected endpoint. Usually scheduled to run once every few minutes. The loader may also obtain persistence using a registry RUN key.
- Perform anti-infection checks and inject the CRAT DLL into a target process.
- The CRAT DLL isn't dropped or downloaded by the .exe based loader to the endpoint.
- It simply reads the DLL from a hardcoded filepath, un-XORs it using a 4-byte key and the resulting DLL is reflectively injected into a specified target process.
The latest variant of the EXE loader contains the following capabilities/upgrades:
- Establish persistence for itself using two mechanisms:
- Create and run a malicious service on the endpoint to run itself.
- Create a malicious LNK for itself which is persisted via a malicious RUN registry key value.
- Read an implant (most likely CRATv2) into memory and reflectively load it into the loader's process space.
Apart from EXE based loaders, this CRAT also uses DLL based loaders. The DLL loaders carry out the same function of decoding the CRAT DLL and reflectively injecting it into a specified process.
The differences are in the persistence techniques used:
- The DLL loader copies itself to a specified directory and creates a LNK that activates the loader via rundll32.exe
- The LNK file is then persisted across reboots via the registry RUN key: HKCU\Software\Microsoft\windows\CurrentVersion\Run | <Value_Name> = <LNK_filepath>
Cisco Talos discovered another variant of the DLL-based loader that acts as a packager as well. Depending on the option specified, the loader will either:
- Activate CRAT:
- Activate unpacked CRAT DLL:
- Reflectively inject an existing CRAT DLL into a hardcoded process.
- Unpack and activate:
- Extract components of the attack from a RAR archive and execute an accompanying EXE file (Most likely used to load the CRAT DLL).
- The extraction isn't carried out directly. This variant will create a VBS file to run rar.exe to extract CRAT components. Syntax used:
Set s = Wscript.CreateObject("Wscript.Shell"): s.Run """%s"" x -y -p%s ""%s"" ""%s""", 0, TRUE: s.Run """%s\%s""", 0: Set s = Nothing
Set s = Wscript.CreateObject("Wscript.Shell"): s.Run """C:\Users\<username>\AppData\Roaming\WinRar\Rar.exe"" x -y -p[password] ""<path_to_rar_file>\<filename>.rar"" ""<target_dir>""", 0, TRUE: s.Run """<target_dir>\<extracted_exe>.exe""", 0: Set s = Nothing
- Just like the previous DLL loader, this variant will create an LNK file to run the VBS script upon reboot by setting up registry key: HKCU\Software\Microsoft\windows\CurrentVersion\Run | <Value_Name> = <LNK_filepath>
- Package CRAT: This variant of the loader also has the capability to create an archive from a specified file on disk. This functionality may be used to create deployment packages for another part of the infection chain. Syntax used:
"<path_to>\Rar.exe" a -k -r -s -ibck -m5 -df -ep -hp[password] "<filepath_of_rar_archive_to_be_created>.rar" "<file_to_be_archived>"
Infection chain of CRATv2
Evolution Timeline of CRAT and Components
The earliest versions of CRAT discovered were compiled in April 2020. The following is a timeline of events in the lifecycle of CRAT with the introduction/modification of its components at different stages of the engineering process.
Earliest known version of CRAT (v1) created. Limited capabilities and basic string obfuscation. Downloaded by malicious HWPs from an infected Wordpress website.
The following components were first built May 2020:
- EXE loader v1 in early May 2020.
- DLL loader v1 in late May 2020.
- CRATv2 seen for the first time in early May 2020.
- Three CRAT plugins seen for the first time in early May 2020.
- Screen Recorder.
- Clipboard Monitor.
- DLL loader v2 first seen in June 2020.
- EXE loader v1 continues evolving to add more persistence mechanisms (LNK and registry Run key combination) in July 2020.
- Ransomware plugin - Hansom spotted in the wild.
- EXE loader v2 first seen in August 2020.
- Latest version of the Ransomware plugin spotted in mid September.
This timeline shows that the attackers have been busy developing a new component of the infection chain almost every month since April 2020.
A visual timeline of the evolution is presented here:
Visual timeline of the evolution of the infection chain of CRAT.
Links to Lazarus
Attribution is hard. Although prior reporting has linked CRAT to Lazarus, there has been no solid evidence to back these claims. There are however some aspects of the attack that resemble Lazarus' practices:
- Code Reuse - CRAT uses the same HTTP wrapper library used by other Lazarus implants such as Wild Positron and Rising Sun. Although this may be a weak attribution link, it does make sense for the group to reuse code they've had success with in the past.
- Functionality Duplication - Lazarus tends to mix-and-match RAT capabilities and peripheral functionalities to stitch together variations of the same implant. That is, different obfuscations mechanisms, communication techniques and RAT capabilities are assembled together to create variations of the implant. This may cause duplication of certain functionalities. In the case of CRAT, the occurrence of the same capability like 'execution of arbitrary commands' multiple times as independent RAT commands and also as part of the File Explorer sub-module indicates a factory-based build approach for the implants. Although a weak link, this process is still in sync with Lazarus' build paradigms.
- Ransomware Plugin - Lazarus has been known to distribute ransomware as a means of sponsoring their malicious activities. The BTC addresses used by the ransomware plugin in the case of CRAT (Hansom Ransomware) do not currently hold any funds. Thus, it is unclear whether this module is in fact ransomware or a pseudo-ransomware (posing as ransomware but meant to burn endpoints).
- Wordpress C2s - CRAT uses Wordpress based websites to act as its C2 servers. This practice is in sync with Lazarus' TTPs of using Wordpress websites to place C2 modules that act as intermediaries between the implants and real C2 servers.
- Past Attribution - CRAT has been attributed to Lazarus in the past by the security community
- Targets - Based on the lures observed so far by Cisco Talos, CRAT aims to infect Korean-speaking entities. This may also be an indicator of Lazarus targeting specific parties of interest.
This investigation illustrates the continued use and evolution of the CRAT implant. CRAT started out as a nascent RAT with limited capabilities, which evolved to introduce a wide variety of malicious capabilities including a full-fledged File Explorer.
The latest iteration of CRAT now has the capability to download and deploy arbitrary plugins on the infected endpoint. These plugins have capabilities ranging from spying to encrypting and holding the user's data hostage. The ransomware plugin in particular has the potential to cause extensive loss of services, time and money to affected organizations.
The continued evolution of loaders used to deploy CRAT also indicates that the attackers are actively developing novel ways of infecting their targets. The extensive use of obfuscation, patching and anti-infection techniques indicates that the attackers have taken great care towards evading detection systems. Thus, while static and network-based detection is important, it should be complimented with system behavior analysis and endpoint protections.
Ways our customers can detect and block this threat are listed below.
Advanced Malware Protection (AMP) is ideally suited to prevent the execution of the malware detailed in this post. Below is a screenshot showing how AMP can protect customers from this threat. Try AMP for free here.
Cisco Cloud Web Security (CWS) or Web Security Appliance (WSA) web scanning prevents access to malicious websites and detects malware used in these attacks.
Email Security can block malicious emails sent by threat actors as part of their campaign.
Network Security appliances such as Next-Generation Firewall (NGFW), Next-Generation Intrusion Prevention System (NGIPS), and Meraki MX can detect malicious activity associated with this threat.
Threat Grid helps identify malicious binaries and build protection into all Cisco Security products.
Umbrella, our secure internet gateway (SIG), blocks users from connecting to malicious domains, IPs and URLs, whether users are on or off the corporate network.
Additional protections with context to your specific environment and threat data are available from the Firepower Management Center.
Open Source Snort Subscriber Rule Set customers can stay up to date by downloading the latest rule pack available for purchase on Snort.org.
Cisco AMP users can use Orbital Advanced Search to run complex OSqueries to see if their endpoints are infected with this specific threat. For specific OSqueries on this threat, click here.
CRATV1 DOWNLOAD LOCATIONS
EXE LOADERS V1
EXE LOADERS V2
DLL LOADERS V1
DLL LOADERS V2 (LOADERS/PACKAGERS)
PLUGINS: HANSOM RANSOMWARE
- CRAT2<FileVersionNumber_from_rsrc> E.g. "CRAT188.8.131.52"
The following is the blocklist of the various artifacts checked on the infected endpoint. If any of these are detected the malware stops execution.
VM RELATED PROCESS NAMES
NETWORK ADAPTER DESCRIPTIONS
- VMware Virtual Ethernet Adapter
- VirtualBox Host-Only Ethernet Adapter
- Process Explorer
- Process Monitor
- Files Monitor
- Burp Suite
ANALYSIS TOOLS PROCESS NAMES
Ransomware Plugin Details
bc1q3tdfzfjngzdlup7x50x3tkfs2mx90a85en9z74 [0 BTC as of publication date]
bc1qpy4dn79xyac8ep6a2daupqmxd6c4cxlywq4fe3 [0 BTC as of publication date]
ATTACKER EMAIL ADDRESSES
FILE NAME EXCLUSIONS
FOLDER NAME EXCLUSIONS
The following folders are excluded from the encryption process by the ransomware plugin.
- Program Files
- Tor Browser
- Program Files (x86)
- All Users
- Local Settings