arrow_back
search
close

RANSOM_GENASOM.THBAFH

March 06, 2018
 ALIASES:

Ransom:Win32/Genasom (Microsoft); Mal/Genasom-A (Sophos AV)

 PLATFORM:

Windows

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

  • Threat Type: Ransomware

  • Destructiveness: No

  • Encrypted: No

  • In the wild: Yes

  OVERVIEW

Infection Channel:

Dropped by other malware, Downloaded from the Internet

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 is capable of encrypting files in the affected system.

It encrypts files with specific file extensions. It encrypts files found in specific folders.

  TECHNICAL DETAILS

File Size:

32,256 bytes

File Type:

EXE

Memory Resident:

No

Initial Samples Received Date:

13 Feb 2018

Payload:

Displays windows, Encrypts files

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.

Other Details

This Ransomware is capable of encrypting files in the affected system.

Ransomware Routine

This Ransomware encrypts files with the following extensions:

  • .doc
  • .docx
  • .xls
  • .xlsx
  • .ppt
  • .pptx
  • .txt
  • .jpg
  • .png
  • .gif
  • .dng
  • .mp3
  • .mp4
  • .rmvb
  • .flac
  • .ape
  • .avi
  • .mkv
  • .mpg
  • .jpeg
  • .pdf

It encrypts files found in the following folders:

  • %User Profile%\

(Note: %User Profile% is the current user's profile folder, which is usually C:\Documents and Settings\{user name} on Windows 2000, XP, and Server 2003, or C:\Users\{user name} on Windows Vista and 7.)

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

  • .干物妹！

NOTES:
Upon execution, this ransomware displays the following window:

  SOLUTION

Minimum Scan Engine:

9.850

FIRST VSAPI PATTERN FILE:

13.970.05

FIRST VSAPI PATTERN DATE:

16 Feb 2018

VSAPI OPR PATTERN File:

13.971.00

VSAPI OPR PATTERN Date:

17 Feb 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

Restart in Safe Mode

[ Learn More ]

Step 4

Identify and terminate files detected as RANSOM_GENASOM.THBAFH

[ Learn More ]
  1. 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.
  2. 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.
  3. If the detected file is not displayed in either Windows Task Manager or Process Explorer, continue doing the next steps.

Step 5

Restart in normal mode and scan your computer with your Trend Micro product for files detected as RANSOM_GENASOM.THBAFH. 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 6

Restore encrypted files from backup.

Step 7

Scan your computer with your Trend Micro product to delete files detected as RANSOM_GENASOM.THBAFH. 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:


Did this description help? Tell us how we did.