Malware Defense History

by Dr. Nikolai Bezroukov.

Copyright: Dr. Nikolai Bezroukov 1994-2013. Unpublished notes. Version 0.80.October, 2013

Contents : Foreword : Ch01 : Ch02 : Ch03  : Ch04 : Ch05 : Ch06 : Ch07 : Ch08 : Ch09 : Ch10 : Ch11 : Ch12 : Ch13

Chapter 7: Network worms

W32/HLLP.Philis Win32/Looked File Infecting Worm

Also known as W32/Downloader (F-Secure), W32/HLLP.Philis (McAfee), Win32.Looked, Win32/Looked!Dropped!Worm, W32.Looked.P (Symantec), W32/Looked-AV (Sophos), Worm.Win32.Viking (Kaspersky)

Based on your sample Phillis/Looked is a file-infecting worm that spreads via network shares. The size of executable is 72,316-bytes compressed Win32 executable. The worm also drops a 33,680-byte DLL which is used to download and execute binary executables.

Virus does infects most or all .EXE file it finds on accessible partitions during the initial launch. Infected files are larger then original by 72/73K (72316 to be exact). The virus scans all the drives it can reach on startup. So if server has some network drives mapped, the results are predictable -- all EXE files on remote drives are infected. It looks like newly mounted partitions  (for example USB drives mounted after computer was infected) are unaffected

If the server is infected with several worms executables like algore.exe  they are infected too :-).

McAfee

W32/HLLP.Philis.gg is a file infecting virus. It searches for executable files on the infected machine to prepend its viral code.

It is also responsible for dropping a DLL file, which downloads password stealing trojans.

TrendMicro

PE_LOOKED.DA - Technical details

Upon execution, it drops and executes the files RUNDL132.EXE and LOGO1_.EXE, which are copies of PE_LOOKED.DA-O, in the Windows folder. It also drops the file DLL.DLL in the folder where it is executed. The said file is detected as TROJ_LOOKED.DZ.

The said DLL file is injected into EXPLORER.EXE process and is responsible for this malware's network propagation routine.

It creates the following registry entry on Windows 98 and ME systems to enable its automatic execution at every system startup:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows\CurrentVersion\Run
Load = "%Windows%\rundl132.exe"

(Note: %Windows% is the Windows folder, which is usually C:\Windows.)

On Windows NT-based (Windows NT, 2000, XP, and Server 2003) systems, it modifies the following registry entry as its autostart technique:

HKEY_CURRENT_USER\Software\Microsoft\
Windows NT\CurrentVersion\Windows
Load = "%Windows%\rundl132.exe"

(Note: The default value of the said entry is Load = "".)

It also creates the following registry key and entry as part of its installation routine:

HKEY_LOCAL_MACHINE\SOFTWARE\Soft\DownloadWWW
Auto = "1"

Propagation via Network Shares and File Infection Routine

This malware attempts to propagate via network shares. It attempts to open shared folders using administrator and guest as user names and blank as password to gain access to the following default shares:

• ADMIN$
• IPC$

It searches for the following .EXE files in drives C to Z and prepends its code to the target file:

• ACDSee4.exe
• ACDSee5.exe
• ACDSee6.exe
• AgzNew.exe
• Archlord.exe
• AutoUpdate.exe
• BNUpdate.exe
• Datang.exe
• editplus.exe
• EXCEL.EXE
• flashget.exe
• foxmail.exe
• FSOnline.exe
• GameClient.exe
• jxonline_t.exe
• launcher.exe
• lineage.exe
• LineageII.exe
• MHAutoPatch.exe
• msimn.exe
• msnmsgr.exe
• Mu.exe
• NATEON.exe
• NSStarter.exe
• Patcher.exe
• patchupdate.exe
• QQ.exe
• Ragnarok.exe
• realplay.exe
• run.exe.
• Silkroad.exe
• Thunder.exe
• ThunderShell.exe
• TTPlayer.exe
• Uedit32.exe
• Winrar.exe
• WINWORD.EXE
• woool.exe
• zfs.exe

In addition, it drops _DESKTOP.INI in every folder it traverses. The said file contains the date of system infection.

Process Termination

This malware terminates the following security-related processes:

• MCSHIELD.EXE
• REGSVC.EXE

It also attempts to stop the service Kingsoft Antivirus Service if found running on the affected system.

Other Details

This file infector runs on Windows 98, ME, NT, 2000, XP, and Server 2003.

Analysis By: Gus Vincent T. Dato
 

Revision History:

Sep 16, 2006 - Inserted Automatic Removal Instructions
Sep 18, 2006 - Modified Virus Report

Symantec

Symantec Security Response - W32.Looked.P

Discovered on: July 12, 2006 Last Updated on: November 01, 2006 11:24:38 AM W32.Looked.P is a worm that spreads through network shares and attempts to infect .exe files. It also lowers security settings and downloads and executes a remote file.
 

Type: Worm Systems Affected: Windows 2000, Windows 95, Windows 98, Windows Me, Windows NT, Windows Server 2003, Windows XP        

Virus Definitions (LiveUpdate™ Plus) July 12, 2006 Virus Definitions (LiveUpdate™ Daily) July 12, 2006 Virus Definitions (LiveUpdate™ Weekly) July 12, 2006 Virus Definitions (Intelligent Updater) July 12, 2006

Wild Number of infections: 0 - 49 Number of sites: 0 - 2 Geographical distribution: Low Threat containment: Easy Removal: Moderate

Damage

• Payload Trigger: n/a
• Payload: n/a
  • Large scale e-mailing: n/a
  • Deletes files: n/a
  • Modifies files: Searches for .exe files to infect in all the drives from C to Y.
  • Degrades performance: n/a
  • Causes system instability: n/a
  • Releases confidential info: n/a
  • Compromises security settings: n/a

Distribution

• Subject of email: n/a
• Name of attachment: n/a
• Size of attachment: n/a
• Time stamp of attachment: n/a
• Ports: n/a
• Shared drives: n/a
• Target of infection: n/a

When W32.Looked.P is executed, it performs the following actions:

1. Creates the following files:
    
   • %Windir%\rundl132.exe - a copy of W32.Looked.P
   • %Windir%\logo1_.exe - a copy of W32.Looked.P
   • %Windir%\dll.dll - a copy of Downloader
   • %CurrentFolder%\vDll.dll - a copy of Downloader
     
     Note:
      
   • %Windir% is a variable that refers to the Windows installation folder. By default, this is C:\Windows or C:\Winnt.
      
   • %CurrentFolder% is a variable that refers to the folder where the risk was originally executed.
     
      
2. Checks for the value:
   
   "auto" = "1"
   
   to the registry subkey:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Soft\DownloadWWW
   
   and either creates the infection marker or exits if it is found.
   
    
3. Adds the value:
   
   "load" = "%Windir%\rundl132.exe"
   
   to the registry subkeys:
   
   HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
   
   so that it runs every time Windows starts.
   
    
4. Attempts to stop the following service:
   
   Kingsoft AntiVirus Service
   
    
5. Injects its DLL component, dll1.dll, into either iexplorer.exe or explorer.exe.
   
    
6. Ends the following processes, some of which are security-related:
   
    
   • Eghost.exe
   • Mailmon.exe
   • Kavpfw.exe
   • Iparmor.exe
   • Ravmond.exe
   • Regsvc.exe
   • Mcshield.exe
     
      
7. Closes the following windows:
   
    
   • Ravmon.exe
   • RavMonClass
     
      
8. Using the DLL component, attempts to download a file from the following location:
   
   [http://]www.wowchian.com/dl[2 LETTERS[REMOVED]
   
    
9. Searches for .exe files to infect in all the drives from C to Y.
   
    
10. Prepends itself to any .exe files that it locates on the computer.
    
     
11. The worm creates the file _desktop.ini in any any directory it has searched for executable files in. This file has the hidden and system attributes set and it stores the date the worm was executed.
    
     
12. Does not infect .exe files in folders with the following names:
    
     
    • system
    • system32
    • windows
    • Documents and Settings
    • System Volume Information
    • Recycled
    • winnt
    • Program Files
    • Windows NT
    • WindowsUpdate
    • Windows Media Player
    • Outlook Express
    • Internet Explorer
    • ComPlus Applications
    • NetMeeting
    • Common Files
    • Messenger
    • Microsoft Office
    • InstallShield Installation Information
    • MSN
    • Microsoft Frontpage
    • Movie Maker
    • MSN Gaming Zone
      
       
13. May send ICMP packets containing the string "Hello,World" to the following IP addresses:
    
     
    • 192.168.0.30
    • 192.168.8.1
      
       
14. May also send ICMP packets to IP addresses in the same range as the IP address of the compromised computer.
     
15. Attempts to open shared folders with the following names, if any computer responds to the ICMP packet:
     
    • \\ipc$
    • \\admin$
       
16. Tries to open the shared folder using administrator as the username and a blank password. It copies itself to that folder, if it succeeds in opening the shared folder.
     
17. Enumerates all the computers and shared folders in the local network. The worm uses a blank username and a blank password to open the shared folders.
     
18. Searches for and infects .exe files in the shared folders.

Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

• Turn off and remove unneeded services. By default, many operating systems install auxiliary services that are not critical, such as an FTP server, telnet, and a Web server. These services are avenues of attack. If they are removed, blended threats have less avenues of attack and you have fewer services to maintain through patch updates.
• If a blended threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
• Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services (for example, all Windows-based computers should have the current Service Pack installed.). Additionally, please apply any security updates that are mentioned in this writeup, in trusted Security Bulletins, or on vendor Web sites.
• Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
• Configure your email server to block or remove email that contains file attachments that are commonly used to spread viruses, such as .vbs, .bat, .exe, .pif and .scr files.
• Isolate infected computers quickly to prevent further compromising your organization. Perform a forensic analysis and restore the computers using trusted media.
• Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.

The following instructions pertain to all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.
 

1. Disable System Restore (Windows Me/XP).
2. Update the virus definitions.
3. Run a full system scan.
4. Delete any values added to the registry.
    

For specific details on each of these steps, read the following instructions.

1. To disable System Restore (Windows Me/XP)
If you are running Windows Me or Windows XP, we recommend that you temporarily turn off System Restore. Windows Me/XP uses this feature, which is enabled by default, to restore the files on your computer in case they become damaged. If a virus, worm, or Trojan infects a computer, System Restore may back up the virus, worm, or Trojan on the computer.

Windows prevents outside programs, including antivirus programs, from modifying System Restore. Therefore, antivirus programs or tools cannot remove threats in the System Restore folder. As a result, System Restore has the potential of restoring an infected file on your computer, even after you have cleaned the infected files from all the other locations.

Also, a virus scan may detect a threat in the System Restore folder even though you have removed the threat.

For instructions on how to turn off System Restore, read your Windows documentation, or one of the following articles:

• How to disable or enable Windows Me System Restore
• How to turn off or turn on Windows XP System Restore

Note: When you are completely finished with the removal procedure and are satisfied that the threat has been removed, reenable System Restore by following the instructions in the aforementioned documents.

For additional information, and an alternative to disabling Windows Me System Restore, see the Microsoft Knowledge Base article: Antivirus Tools Cannot Clean Infected Files in the _Restore Folder (Article ID: Q263455).

2. To update the virus definitions
Symantec Security Response fully tests all the virus definitions for quality assurance before they are posted to our servers. There are two ways to obtain the most recent virus definitions:

• Running LiveUpdate, which is the easiest way to obtain virus definitions:
  • If you use Norton AntiVirus 2006, Symantec AntiVirus Corporate Edition 10.0, or newer products, LiveUpdate definitions are updated daily. These products include newer technology.
  • If you use Norton AntiVirus 2005, Symantec AntiVirus Corporate Edition 9.0, or earlier products, LiveUpdate definitions are updated weekly. The exception is major outbreaks, when definitions are updated more often.
• Downloading the definitions using the Intelligent Updater: The Intelligent Updater virus definitions are posted daily. You should download the definitions from the Symantec Security Response Web site and manually install them. To determine whether definitions for this threat are available by the Intelligent Updater, refer to Virus Definitions (Intelligent Updater).
  
  The latest Intelligent Updater virus definitions can be obtained here: Intelligent Updater virus definitions. For detailed instructions read the document: How to update virus definition files using the Intelligent Updater.

3. To run a full system scan

1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
   • For Norton AntiVirus consumer products: Read the document: How to configure Norton AntiVirus to scan all files.
   • For Symantec AntiVirus Enterprise products: Read the document: How to verify that a Symantec Corporate antivirus product is set to scan all files.
2. Run a full system scan.
3. If any files are detected, follow the instructions displayed by your antivirus program.

Important: If you are unable to start your Symantec antivirus product or the product reports that it cannot delete a detected file, you may need to stop the risk from running in order to remove it. To do this, run the scan in Safe mode. For instructions, read the document, How to start the computer in Safe Mode. Once you have restarted in Safe mode, run the scan again.

After the files are deleted, restart the computer in Normal mode and proceed with the next section.

Warning messages may be displayed when the computer is restarted, since the threat may not be fully removed at this point. You can ignore these messages and click OK. These messages will not appear when the computer is restarted after the removal instructions have been fully completed. The messages displayed may be similar to the following:

Title: [FILE PATH]
Message body: Windows cannot find [FILE NAME]. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

4. To delete the value from the registry
Important: Symantec strongly recommends that you back up the registry before making any changes to it. Incorrect changes to the registry can result in permanent data loss or corrupted files. Modify the specified subkeys only. For instructions refer to the document: How to make a backup of the Windows registry.
 

1. Click Start > Run.
2. Type regedit
3. Click OK.
   
   Note: If the registry editor fails to open the threat may have modified the registry to prevent access to the registry editor. Security Response has developed a tool to resolve this problem. Download and run this tool, and then continue with the removal.
   
    
4. Navigate to the subkeys:
   
   HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
   
    
5. In the right pane, delete the value:
   
   "load" = "%Windir%\rundl132.exe"
   
    
6. Exit the Registry Editor.

CA

Win32-Looked.S