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/Sality.o

This page shows details and results of our analysis on the malware W32/Sality.o

Threat Detail

Malware Type: Virus

Malware Sub-type: Win32

Discovery Date: 2006-02-14

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

4696 (2006-02-14)

Updated DAT

4698 (2006-02-16)

 Minimum Engine

5400.1158

File Length

Varies

 Description Added

2006-02-14

Description Modified

2006-02-15

Malware Proliferation

Characteristics

The W32/Sality.o detection covers PE files that are partially infected with a W32/Sality variant. However, unlike other W32/Sality infections, W32/Sality.o does not contain the core W32/Sality.dll component. The entry point of such PE files has been overwritten by the Sality virus, and the original entry point is encrypted within the last PE section of infected files. Even in this state, W32/Sality.o infected files are repairable.

At the time of this writing, the only W32/Sality.o infected files received by AVERT are variants of the W32/Bagle virus (these are what is known as cocktails, multiply infected files; in this case:

( W32/Sality.o ( W32/Bagle ))

Upon removing the W32/Sality.o infection, W32/Bagle is then identified.

W32/Bagle.dt@MM  is one such cocktail known to be spreading.

Symptoms

.EXE files increasing in file size.

Method of Infection

W32/Sality.o may not be viable in W32/Bagle cocktail form.  However, it does not prevent W32/Bagle from replicating successfully.

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