Analysis by: Alyssa Christelle Ramos
ALIASES:

Trojan.Win32.Crypt(IKARUS)

 PLATFORM:

Windows

 OVERALL RISK RATING:
 DAMAGE POTENTIAL:
 DISTRIBUTION POTENTIAL:
 REPORTED INFECTION:
 INFORMATION EXPOSURE:

  • Threat Type: Ransomware

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

Infection Channel: Downloaded from the Internet, 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 avoids encrypting files with the following file extensions.

  TECHNICAL DETAILS

File Size: 569,856 bytes
File Type: EXE
Memory Resident: Yes
Initial Samples Received Date: 09 Feb 2020
Payload: Encrypts files in fixed, remote, and network drives and resources

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 adds the following processes:

  • /c del {malware file path and name}>> NUL -> deletes itself

Process Termination

This Ransomware terminates the following processes if found running in the affected system's memory:

  • MySQL
  • MYSQL80
  • MSSQLSERVER
  • SQLWriter
  • MSDTC
  • SQLBrowser
  • sqlservr.exe
  • sqlwriter.exe
  • msdtc.exe
  • sqlbrowser.exe

Other Details

This Ransomware does the following:

  • It encrypts Fixed and Remote/Network drives.
  • It encrypts files in Network resources.
  • It accepts the following arguments:
    • net ->deletes itself and will not perform its routine
    • local -> perform its routine

Ransomware Routine

This Ransomware avoids encrypting files found in the following folders:

  • %Windir%
  • C:\Boot
  • C:\Config.msi
  • C:\$Recycle Bin
  • C:\System Volume Information
  • C:\Recovery
  • C:\Documents and Settings
  • C:\ProgramData
  • C:\Program Files\Microsoft Office
  • C:\Program Files (x86)\Microsoft Office

It appends the following extension to the file name of the encrypted files:

  • {Original Filename}.{Original Extension}.cuba

It leaves text files that serve as ransom notes containing the following text:

  • !!FAQ for Decryption!!.txt

It avoids encrypting files with the following file extensions:

  • .exe
  • .dll
  • .sys
  • .cuba

  SOLUTION

Minimum Scan Engine: 9.850
FIRST VSAPI PATTERN FILE: 15.676.09
FIRST VSAPI PATTERN DATE: 07 Feb 2020
VSAPI OPR PATTERN File: 15.677.00
VSAPI OPR PATTERN Date: 08 Feb 2020

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.XXPE50FFF033

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

Restart in Safe Mode

[ Learn More ]

Step 5

Search and delete these files

[ Learn More ]
There may be some files that are hidden. Please make sure you check the Search Hidden Files and Folders checkbox in the "More advanced options" option to include all hidden files and folders in the search result.
  • !!FAQ for Decryption!!.txt

Step 6

Restart in normal mode and scan your computer with your Trend Micro product for files detected as Ransom.Win32.LEDIF.A. 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 this Knowledge Base page for more information.

Step 7

Restore encrypted files from backup.


Did this description help? Tell us how we did.