McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
Business Home → McAfee Labs → Threat Intelligence

BackDoor-CZX

This page shows details and results of our analysis on the malware BackDoor-CZX

Threat Detail

Malware Type: Trojan

Malware Sub-type: Remote Access

Discovery Date: 2006-05-24

Next Steps:

Overview

This is a trojan detection. Unlike viruses, trojans do not self-replicate. They are spread manually, often under the premise that they are beneficial or wanted. The most common installation methods involve system or security exploitation, and unsuspecting users manually executing unknown programs. Distribution channels include email, malicious or hacked web pages, Internet Relay Chat (IRC), peer-to-peer networks, etc.


Minimum DAT

4769 (2006-05-24)

Updated DAT

4769 (2006-05-24)

 Minimum Engine

5.1.00

File Length

34,119

 Description Added

2006-05-24

Description Modified

2006-05-29

Malware Proliferation

Characteristics

Upon execution, the trojan drops the following files.

%SYSTEMDIR%\abcedg.dll ( 19456 bytes )
%SYSTEMDIR%\stdole.tbl 

The following registry keys are created to install the dll as LSP (Layered Service Provider) to the TCP/IP protocol stack.

NOTE: The keys added under WinSock2\Parameters may vary in their numbering and/or values depending on the state of the LSP stack at the time of installation.

  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000001
    \packedcatalogitem="%SYSTEMDIR%\abcedg.dll"
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000002
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000003
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000004
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000005
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000006
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000007
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000008
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000009
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000010
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000011
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000012
    \packedcatalogitem="(binary registry data)
  • hkey_local_machine\system\currentcontrolset\services\winsock2
    \parameters\protocol_catalog9\catalog_entries\000000000013
    \packedcatalogitem="(binary registry data)

 

The trojan connects 218.57.[Removed] at port 1443 and sends the system information such as CPU, IP address and UserName.

Then it connects the remote host at port 1444 and provide a remote shell.

Symptoms

  • Presence of mentioned registry keys and files

Method of Infection

Trojans do not self-replicate. They are spread manually, often under the premise that the executable is something beneficial. Distribution channels include IRC, peer-to-peer networks, newsgroup postings, etc. 

Removal

All Users:
Use current engine and DAT files for detection and removal.

Modifications made to the system Registry and/or INI files for the purposes of hooking system startup, will be successfully removed if cleaning with the recommended engine and DAT combination (or higher).

But in some particular cases, the following steps need to be taken.

Please go to the Microsoft Recovery Console and restore a clean MBR.

On Windows XP:

  • Insert the Windows XP CD into the CD-ROM drive and restart the computer.
  • When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
  • Select the Windows installation that is compromised and provide the administrator password.
  • Issue 'fixmbr' command to restore the Master Boot Record
  • Follow onscreen instructions.
  • Reset and remove the CD from CD-ROM drive.


On Windows Vista and 7:

  • Insert the Windows CD into the CD-ROM drive and restart the computer.
  • Click on "Repair Your Computer".
  • When the System Recovery Options dialog comes up, choose the Command Prompt.
  • Issue 'bootrec /fixmbr' command to restore the Master Boot Record.
  • Follow onscreen instructions.
  • Reset and remove the CD from CD-ROM drive.

Variants

United States - English