Analysis by: Anthony Joe Melgarejo

ALIASES:

Trojan:Win32/Alureon.GC (Microsoft), W32/Injector.ZVR!tr (Fortinet), Trojan.Win32.Spy2.RP (Ikarus), a variant of Win32/Injector.AFXT trojan (ESET)

 PLATFORM:

Windows 2000, Windows Server 2003, Windows XP (32-bit, 64-bit), Windows Vista (32-bit, 64-bit), Windows 7 (32-bit, 64-bit)

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

  • Threat Type: Backdoor

  • Destructiveness: No

  • Encrypted:

  • In the wild: Yes

  OVERVIEW

Infection Channel: Downloaded from the Internet, Dropped by other malware

This malware uses multi-protocol instant-messaging applications in order to propagate itself. It also has backdoor routines that steal login information from the affected system's browsers. Users with systems infected with this malware may have their online banking accounts compromised.

To get a one-glance comprehensive view of the behavior of this Backdoor, refer to the Threat Diagram shown below.

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

It runs certain commands that it receives remotely from a malicious user. Doing this puts the affected computer and information found on the computer at greater risk.

  TECHNICAL DETAILS

File Size: 317,952 bytes
File Type: EXE
Memory Resident: Yes
Initial Samples Received Date: 29 Apr 2013
Payload: Connects to URLs/IPs, Compromises system security

Arrival Details

This backdoor 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 backdoor drops the following copies of itself into the affected system and executes them:

  • %All Users Profile%\Application Data\{random letters}sacfsfdsf.exe

(Note: %All Users Profile% is the All Users or Common profile folder, which is C:\Documents and Settings\All Users in Windows 2000, XP, and Server 2003, and C:\ProgramData in Windows Vista and 7.)

It adds the following mutexes to ensure that only one of its copies runs at any one time:

  • {random string}sacfsfdsf

It injects itself into the following processes as part of its memory residency routine:

  • explorer.exe

It terminates the execution of the copy it initially executed and executes the copy it drops instead.

Autostart Technique

This backdoor adds the following registry entries to enable its automatic execution at every system startup:

HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Run
{random letters}sacfsfdsf = "%All Users Profile%\Application Data\{random letters}sacfsfdsf.exe"

Other System Modifications

This backdoor adds the following registry keys:

HKEY_CURRENT_USER\Software\{random letters}sacfsfdsf

It adds the following registry entries:

HKEY_CURRENT_USER\Software\{random letters}sacfsfdsf
CurrentPath111 = "%All Users Profile%\Application Data\{random letters}sacfsfdsf.exe"

Backdoor Routine

This backdoor executes the following command(s) from a remote malicious user:

  • Download and execute arbitrary files
  • Update itself
  • Inject arbitrary routines to a running process
  • Send logs
  • Edit configuration

It connects to the following URL(s) to send and receive commands from a remote malicious user:

  • http://{BLOCKED}.{BLOCKED}on.pl/p/c1.php
  • http://{BLOCKED}.{BLOCKED}b.pl/p/c1.php
  • http://{BLOCKED}.{BLOCKED}ws.su/p/c1.php

NOTES:

In this time of writing, this backdoor received commands from its C&C server to download from the following URLs:

  • http://{BLOCKED}9.{BLOCKED}e.com/get/cb31d50f0a86e082dfafb84e78978273a5d1a258/517f8dfd/2/a293a29f1973f998/c55da70/19835y1e87i483
  • http://{BLOCKED}e.com/dl/206953072/6e01dd1/19835y1e87i483.html

It saves the file it downloads using the following name:

  • %All Users Profile%\Application Data\{4 random alphanumeric characters}.exe - detected as WORM_DORKBOT.SME

Its configuration consists of the following:

  • C&C servers
  • Connection timeout
  • Number of max connection attempts
  • Malware build version

The downloaded file by this backdoor can be any of the following:

  • WORM_KUVAA.A
  • WORM_DORKBOT.SME

  SOLUTION

Minimum Scan Engine: 9.300
FIRST VSAPI PATTERN FILE: 9.888.01
FIRST VSAPI PATTERN DATE: 29 Apr 2013
VSAPI OPR PATTERN File: 9.889.00
VSAPI OPR PATTERN Date: 30 Apr 2013

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

Remove malware/grayware files dropped/downloaded by BKDR_LIFTOH.DLF. (Note: Please skip this step if the threats listed below have already been removed.)

Step 3

Restart in Safe Mode

[ Learn More ]

Step 4

Delete this registry value

[ Learn More ]

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
    • {random letters}sacfsfdsf = "%All Users Profile%\Application Data\{random letters}sacfsfdsf.exe"

Step 5

Delete this registry key

[ Learn More ]

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. Before you could do this, you must restart in Safe Mode. For instructions on how to do this, you may refer to this page If the preceding step requires you to restart in safe mode, you may proceed to edit the system registry.

  • In HKEY_CURRENT_USER\Software
    • {random letters}sacfsfdsf

Step 6

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


Did this description help? Tell us how we did.