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

W32/HLLP.Philis.g

This page shows details and results of our analysis on the malware W32/HLLP.Philis.g

Threat Detail

Malware Type: Virus

Malware Sub-type: Parasitic

Discovery Date: 2004-12-15

Next Steps:

Overview

This is a virus detection. Viruses are programs that self-replicate recursively, meaning that infected systems spread the virus to other systems, which then propagate the virus further. While many viruses contain a destructive payload, it's quite common for viruses to do nothing more than spread from one system to another.


Minimum DAT

4411 (2004-12-01)

Updated DAT

4802 (2006-07-07)

 Minimum Engine

5400.1158

File Length

59904

 Description Added

2004-12-01

Description Modified

2004-12-21

Malware Proliferation

Characteristics

W32/HLLP.Philis.g is a file infecting virus.

It searches for 32 bit PE .exe files and prepends its viral code to target files. It adds 59904 bytes infront of the original file so whenever that file is being called the virus code is initiated instead. The prepending virus code is written using Borland Delphi.

It also tries to connect to shared drives using ipc$ . Using a few admininistrator/admin logons it tries to connect to open shares that are not properly protected with passwords.

The virus can be detected and cleaned fine.

The virus carries a trojan component inside for keylogging. The embedded file "virdll.dll " , having a filesize of 14848 bytes, is detected as PWS-LegMir. The file is internally compressed using upx.

Symptoms

  • Modified .exe files
  • Presence of virdll.dll (14848)

Method of Infection

W32/HLLP.Philis.g is a file infecting virus. Infection starts with manual execution of the binary which may rely on not properly configured/protected (open) shared drives.

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