PWS-JK

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

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

4722 (2006-03-20)

Updated DAT

4723 (2006-03-21)

Minimum Engine

5.1.00

File Length

24.202 (exe/sys) , 18.602 (dll)

Description Added

2006-03-17

Description Modified

2006-03-17

Malware Proliferation

Characteristics

Detection was added to provide cover against a malicious 32 bit PE file originally called "temp.exe " , having a filesize of  24.202 bytes decimal. The file is internally compressed with the FSG packer.

Upon running this file, it runs silently, no gui interface or other messageboxes appear. It immediately copies itself as "openglssd.sys " (filesize 24.202) into the %windows\%system directory, for example on win2000: c:\winnt\system32\openglssd.sys.  

It also drops a malicious file called "openglss.dll " (filesize 18.602) into that same directory.

The following registry keys are created:

  • hkey_local_machine\software\microsoft\windows nt\currentversion
    \winlogon\notify\openglss\startup="openglss"
  • hkey_local_machine\software\microsoft\windows nt\currentversion
    \winlogon\notify\openglss\nk48id
  • hkey_local_machine\system\currentcontrolset\services\openglssd
    \imagepath="\??\%WINDIR% \System32\openglssd.sys"

It may connect to websites related to e-gold , fake disguise.

Note that the file "opengl32.dll" is a regular windows system file.

Symptoms

  • Presence of the files/filesizes as mentioned above

Method of Infection

  • Manual execution of the binary starts the infection, there's no exploit associated with this.

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