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

PWS-IX

This page shows details and results of our analysis on the malware PWS-IX

Threat Detail

Malware Type: Trojan

Malware Sub-type: Password Stealer

Discovery Date: 2005-05-30

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

4502 (2005-05-30)

Updated DAT

4502 (2005-05-30)

 Minimum Engine

5.1.00

File Length

45056 , 24576

 Description Added

2005-05-30

Description Modified

2005-06-06

Malware Proliferation

Characteristics

Detection was added to cover for a malicious 32 bit PE file originally called "tjppdd.exe " , having a filesize of 45056 bytes. 

Upon execution of this file, it drops an embedded file that's in the resource directory called "tj_pp.dll ", having a filesize of 24576 bytes.

The files are not internally compressed with packers.

The 2 files are being copied to the %windows\%system directory, for example on a win2k test system:

  • c:\WINNT\system32\tj_pp.dll       (size: 24576 bytes)
  •  c:\WINNT\system32\tjppdd.exe  (size: 45056 bytes)

To automatically launch itself upon system start it makes a registry entry under:

  • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run "tjpp"

The tj_pp.dll file tries to install a systemhook and may capture information from key-type sequences. It then calls a mail routine to send the captured info out by e-mail.

Symptoms

  • Presence of the files/filesizes as mentioned above
  • Presence of the registry key as mentioned above

Method of Infection

  • Manual execution of the binary, there's no known exploit associated with the file.

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