PE_VIRUX.R-2

 Analysis by: jasperm

 ALIASES:

Symantec : W32.Virut.CF; Microsoft : Virus:Win32/Virut.BN; Kaspersky : Virus.Win32.Virut.ce

 PLATFORM:

Windows 2000, XP, Server 2003

 OVERALL RISK RATING:
 DAMAGE POTENTIAL:
 DISTRIBUTION POTENTIAL:
 REPORTED INFECTION:

  • Threat Type: File infector

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

Infection Channel:

Infects files

This file infector infects target host files via EPO-Cavity-Appending infection technique.

It hooks APIs so that when these APIs are called, the virus code is executed which then infect files.

It does not infect files with certain characteristics.

It also searches for target script files for iframe infection. Infected script files are detected as HTML_IFRAME.SMV.

It connects to certain IRC servers and attempts to join a certain channel to receive and execute commands on the affected system.

As of this writing, no reply has been received from the servers.

This file infector may be dropped by other malware. It may be unknowingly downloaded by a user while visiting malicious websites.

It connects to Internet Relay Chat (IRC) servers.

  TECHNICAL DETAILS

File Size:

Varies

File Type:

PE

Memory Resident:

Yes

Initial Samples Received Date:

07 May 2010

Payload:

Modifies HOSTS file, Compromises system security

Arrival Details

This file infector may be dropped by other malware.

It may be unknowingly downloaded by a user while visiting malicious websites.

Installation

This file infector injects threads into the following normal process(es):

  • WINLOGON.EXE

Other System Modifications

This file infector also creates the following registry entry(ies) as part of its installation routine:

HKEY_USERS\.DEFAULT\SOFTWARE\
Microsoft\Windows\CurrentVersion\
Explorer
UpdateHost = {random binary value}

It creates the following registry entry(ies) to bypass Windows Firewall:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\SharedAccess\Parameters\
FirewallPolicy\DomainProfile\AuthorizedApplications\
List
\??\%System%\winlogon.exe = \??\%System \winlogon.exe:*:enabled:@shell32.dll,-1

File Infection

This file infector infects the following files:

  • EXE
  • SCR

It avoids infecting files that contain the following strings in their names:

  • OTSP
  • WC32
  • WCUN
  • WINC

Backdoor Routine

This file infector connects to any of the following Internet Relay Chat (IRC) servers:

  • {BLOCKED}O.brenz.pl
  • {BLOCKED}t.trenz.pl

HOSTS File Modification

This file infector adds the following strings to the Windows HOSTS file:

  • 127.0.0.1 www.{BLOCKED}z.pl

Other Details

Based on analysis of the codes, it has the following capabilities:

  • It hooks the following APIs so that when these APIs are called, the virus code is executed which then infect files:
    • NtCreateFile
    • NtOpenFile
    • NtCreateProcess
    • NtCreateProcessEx
    • NtQueryInformationProcess
  • This file infector infects target host files via EPO-Cavity-Appending infection technique.
  • It does not infect files with the following characteristics:
    • .DLL files
    • PE Files with _win section name
    • Files with infection marker
  • It also infects script files by first checking if the target script file's extension name is any of the following:
    • .ASP
    • .HTM
    • .PHP
  • Once it finds target script files, it creates a flag for the file for iFrame infection. It opens flagged files then checks for a certain string in the file. If it finds that string, it skips the file. If not, then it proceeds with the infection of the file.
  • It then looks for the string in the target script file. Once found, it infects script files by inserting the malicious iFrame code below:
  • It returns execution to the host file's original code after execution.
  • It connects to the said servers using 8-randomly generated character for its NICK and 1-randomly generated character for its USER.
  • Once connected to the IRC server, it joins a certain channel to receive and execute commands on the affected system.
  • As of this writing, no reply has been received from the servers.
  • Infected script files are detected as HTML_IFRAME.SMV.

  SOLUTION

Minimum Scan Engine:

8.900

FIRST VSAPI PATTERN FILE:

7.153.80

FIRST VSAPI PATTERN DATE:

07 May 2010

Step 1

Before doing any scans, Windows XP, Windows Vista, and Windows 7 users must disable System Restore to allow full scanning of their computers.

Step 2

Remove the malware/grayware file dropped/downloaded by PE_VIRUX.R-2

    HTML_IFRAME.SMV

Step 3

Restart in Safe Mode

[ Learn More ]

Step 4

Delete this registry value

[ Learn More ]

Important: Editing the Windows Registry incorrectly can lead to irreversible system malfunction. Please do this step only if you know how or you can ask assistance from your system administrator. Else, check this Microsoft article first before modifying your computer's registry.

  • In HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
    • UpdateHost = {random binary value}
  • In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List
    • \??\System\winlogon.exe = \??\System\winlogon.exe:*:enabled:@shell32.dll,-1

Step 5

Remove these strings added by the malware/grayware/spyware in the HOSTS file

[ Learn More ]

    127.0.0.1 www.{BLOCKED}z.pl

"

Step 6

Scan your computer with your Trend Micro product to clean files detected as PE_VIRUX.R-2. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check this Knowledge Base page for more information.


Did this description help? Tell us how we did.