RANSOM_MAKTUB.BQ

 Analysis by: Francis Xavier Antazo

 ALIASES:

a variant of Win32/Kryptik.ETIA trojan (ESET); HEUR:Trojan.Win32.Generic (Kaspersky);

 PLATFORM:

Windows

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

  • Threat Type: Trojan

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

Infection Channel:

Downloaded from the Internet


This Trojan arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

  TECHNICAL DETAILS

File Size:

296,448 bytes

File Type:

EXE

Memory Resident:

Yes

Initial Samples Received Date:

11 Apr 2016

Payload:

Modifies files, Encrypts files

Arrival Details

This Trojan 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 Trojan drops the following files:

  • %User Temp%\{random filename}.cab - archive containing the RTF document
  • %User Temp%\{malware filename}.rtf - non-malicious document
  • {folders containing encrypted files}\_DECRYPT_INFO_{extension name}.html - ransom note
  • %User Temp%\{extension name}.gif - Maktub Locker logo

(Note: %User Temp% is the user's temporary folder, where it usually is C:\Documents and Settings\{user name}\Local Settings\Temp on Windows 2000, Windows Server 2003, and Windows XP (32- and 64-bit); C:\Users\{user name}\AppData\Local\Temp on Windows Vista (32- and 64-bit), Windows 7 (32- and 64-bit), Windows 8 (32- and 64-bit), Windows 8.1 (32- and 64-bit), Windows Server 2008, and Windows Server 2012.)

Other System Modifications

This Trojan modifies the following file(s):

  • It encrypts files and appends a random extension to the encrypted files

Other Details

This Trojan encrypts files with the following extensions:

  • db0
  • dba
  • dbf
  • dbfv
  • dcr
  • der
  • desc
  • dmp
  • dng
  • doc
  • docm
  • docx
  • dot
  • dotx
  • dwg
  • dxf
  • dxg
  • epk
  • eps
  • erf
  • esm
  • exif
  • ff
  • flv
  • forge
  • fos
  • fpk
  • fsh
  • gdb
  • gho
  • hkdb
  • hkx
  • hplg
  • htm
  • hvpl
  • ibank
  • icxs
  • ifo
  • indd
  • itdb
  • itl
  • itm
  • iwd
  • iwi
  • jfif
  • jpe
  • jpeg
  • jpg
  • js
  • kdb
  • kdc
  • kf
  • layout
  • lbf
  • litemod
  • lrf
  • ltx
  • lvl
  • m2
  • m3u
  • m4a
  • map
  • mcgame
  • mcmeta
  • mdb
  • mdbackup
  • mddata
  • mdf
  • mef
  • menu
  • mht
  • mlx
  • mov
  • mp4
  • mpg
  • mpp
  • mpqge
  • mrw
  • mrwref
  • msg
  • ncf
  • nef
  • nrw
  • ntl
  • odb
  • odc
  • odm
  • odp
  • ods
  • odt
  • orf
  • p12
  • p7b
  • p7c
  • pak
  • pdd
  • pdf
  • pef
  • pem
  • pfx
  • pgp
  • pkpass
  • png
  • ppsx
  • ppt
  • pptm
  • pptx
  • psd
  • psk
  • pst
  • ptx
  • py
  • qdf
  • qic
  • r3d
  • raf
  • raw
  • rb
  • rdp
  • re4
  • rgss3a
  • rim
  • rofl
  • rtf
  • rw2
  • rwl
  • sav
  • sb
  • sc2save
  • shs
  • sid
  • sidd
  • sidn
  • sie
  • sis
  • slm
  • snx
  • sql
  • sr2
  • srf
  • srw
  • sum
  • svg
  • syncdb
  • t12
  • t13
  • tax
  • tc
  • thm
  • thmx
  • tif
  • tor
  • txt
  • unity3d
  • upk
  • vcf
  • vdf
  • vfs0
  • vob
  • vpk
  • vpp_pc
  • vsd
  • vtf
  • w3x
  • wallet
  • wb2
  • wma
  • wmo
  • wmv
  • wotreplay
  • wpd
  • wps
  • x3f
  • xf
  • xlk
  • xls
  • xlsb
  • xlsm
  • xlsx
  • xxx
  • ztmp

NOTES:

This malware does not encrypt files contained in the following folders:

  • \appdata\
  • \chache\
  • \chaches\
  • \chrome\
  • \history\
  • \internet explorer\
  • \microsoft\
  • \mozilla\
  • \program files (x86)\
  • \program files\
  • \temp\

It opens the dropped document file:

It displays the following window after file encryption:

The dropped html component contains the ransom note:

Upon visiting the website, it asks for the decryption key:

It then redirects users to main webpage:

  SOLUTION

Minimum Scan Engine:

9.800

FIRST VSAPI PATTERN FILE:

12.460.04

FIRST VSAPI PATTERN DATE:

11 Apr 2016

VSAPI OPR PATTERN File:

12.461.00

VSAPI OPR PATTERN Date:

12 Apr 2016

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_MAKTUB.BQ

[ 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 4

Search and delete this file

[ 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.
  • %User Temp%\{random filename}.cab
  • %User Temp%\{malware filename}.rtf
  • %User Temp%\{extension name}.gif
  • {folders containing encrypted files}\_DECRYPT_INFO_{extension name}.html

Step 5

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


Did this description help? Tell us how we did.