BKDR_KULUOZ.SM15

 Analysis by: RonJay Kristoffer Caragay

 ALIASES:

TrojanDownloader:Win32/Kuluoz.D (Microsoft); Win32/TrojanDownloader.Zortob.H (ESET-NOD32); TrojanDownloader.Kuluoz.AA4 (CAT-QuickHeal); Troj/Weelsof-JD (Sophos); Backdoor/Win32.Kuluoz (AhnLab-V3)

 PLATFORM:

Windows

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

  • Threat Type: Backdoor

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

Infection Channel:

Spammed via email

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 executes commands from a remote malicious user, effectively compromising the affected system. It connects to a website to send and receive information.

  TECHNICAL DETAILS

File Size:

86,528 bytes

File Type:

EXE

Memory Resident:

Yes

Initial Samples Received Date:

04 Nov 2014

Payload:

Collects system information, Connects to URLs/IPs

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:

  • %AppDataLocal%\{random filename}.exe

(Note: %AppDataLocal% is the Application Data folder found in Local Settings, where it is usually C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000, Windows Server 2003, and Windows XP (32- and 64-bit); C:\Users\{user name}\AppData\Local 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.)

It adds the following processes:

  • svchost.exe

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

  • aa{User Name}
  • ab{User Name}

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

  • created svchost.exe

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} = "%AppDataLocal%\{random filename}.exe"

Other System Modifications

This backdoor adds the following registry keys:

HKEY_CURRENT_USER\SOFTWARE\{random}

It adds the following registry entries:

HKEY_CURRENT_USER\SOFTWARE\{random}
{random} = "{hex values}"

Backdoor Routine

This backdoor executes the following commands from a remote malicious user:

  • idl - sleep/idle
  • run - download and execute arbitrary file
  • rem - uninstall itself
  • rdl - update copy of injected code in svchost and add encrypted code to registry
  • upd - update copy of main malware
  • red - edit registry
  • ear - update copy of malware and autorun registry entry

It connects to the following websites to send and receive information:

  • http://{BLOCKED}.{BLOCKED}.78.225:8080/index.php
  • http://{BLOCKED}.{BLOCKED}.37.14:443/index.php
  • http://{BLOCKED}.{BLOCKED}.210.196:3128/index.php
  • http://{BLOCKED}.{BLOCKED}.238.77:8080/index.php
  • http://{BLOCKED}.{BLOCKED}.147.7:8080/index.php
  • http://{BLOCKED}.{BLOCKED}.19.242:8080/index.php
  • http://{BLOCKED}.{BLOCKED}.42.104:8080/index.php

NOTES:

It checks if there's a running window with the following name:

  • wireshark.exe
  • Tfrmrpcap
  • iptools.exe
  • Iris - Version 5.59
  • ProcessLasso_Notification_Class
  • TSystemExplorerTrayForm.UnicodeClass
  • PROCMON_WINDOW_CLASS
  • PROCEXPL
  • WdcWindow
  • ProcessHacker
  • 99929D61-1338-48B1-9433-D42A1D94F0D2-x64
  • 99929D61-1338-48B1-9433-D42A1D94F0D2-x32
  • 99929D61-1338-48B1-9433-D42A1D94F0D2
  • Dumper
  • Dumper64
  • APISpy32Class
  • VMwareDragDetWndClass
  • VMwareSwitchUserControlClass
  • vmtoolsd.exe
  • prl_cc.exe
  • prl_tools.exe
  • SharedIntApp.exe
  • VBoxTray.exe
  • VBoxService.exe
  • vmusrvc.exe
  • vmsrvc.exe

It checks the Service Disk or Bios registries if the following is under Virtualization:

  • VMWare
  • PTLTD
  • Virtual
  • PRLS
  • Vbox
  • AMIBI

It checks if the following registry keys exist:

  • SYSTEM\CurrentControlSet\Enum\PCI\VEN_15ADDEV_0774SUBSYS_040515ADREV_00
  • SYSTEM\CurrentControlSet\Enum\PCI\VEN_15ADDEV_0774SUBSYS_074015ADREV_00
  • SYSTEM\CurrentControlSet\Enum\PCI\VEN_5333DEV_8811SUBSYS_00000000REV_00
  • SYSTEM\CurrentControlSet\Enum\PCI\VEN_80EESUBSYS_00000000REV_00
  • SYSTEM\CurrentControlSet\Enum\PCI\VEN_80EESUBSYS_00000000REV_00
  • HARDWARE\ACPI\DSDT\PTLTD__
  • HARDWARE\ACPI\DSDT\VBOX__
  • HARDWARE\ACPI\DSDT\AMIBI

  SOLUTION

Minimum Scan Engine:

9.700

FIRST VSAPI PATTERN FILE:

11.274.02

FIRST VSAPI PATTERN DATE:

13 Nov 2014

VSAPI OPR PATTERN File:

11.275.00

VSAPI OPR PATTERN Date:

13 Nov 2014

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

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} = "%AppDataLocal%\{random filename}.exe"

Step 5

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

The following created files/folders/registry keys/registry entries cannot be identified by the user since there are no reference values in the created key. The only way it can be identified is by comparing the present system information with a backup. Note that the said components do not have to be deleted since it won't be harmful to the system.

 
  • In HKEY_CURRENT_USER\SOFTWARE
    • {random}


Did this description help? Tell us how we did.