W32.HLLW.Winur.B

Printer Friendly Page

Discovered: March 21, 2003
Updated: February 13, 2007 11:45:01 AM
Type: Worm
Systems Affected: Windows


W32.HLLW.Winur.B is a worm that attempts to use the KaZaA or WinMX file-sharing programs, MyWebServer peer-to-peer Personal Web Server, or the ABYSS Web Server program to spread itself.

This threat is written in the Microsoft Visual Basic programming language.

Antivirus Protection Dates

  • Initial Rapid Release version March 24, 2003
  • Latest Rapid Release version September 28, 2010 revision 054
  • Initial Daily Certified version March 24, 2003
  • Latest Daily Certified version September 28, 2010 revision 036
  • Initial Weekly Certified release date March 25, 2003

Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

Writeup By: Yana Liu

Discovered: March 21, 2003
Updated: February 13, 2007 11:45:01 AM
Type: Worm
Systems Affected: Windows


When W32.HLLW.Winur.B runs, it does the following:

  1. Copies itself as:
    • C:\Windows\Winrun.exe
    • C:\Winnt\Winrun.exe
    • C:\Winnt\Profiles\All Users\Programma's\Opstarten\Winrun.exe
    • C:\Winnt\Profiles\All Users\Programs\Startup\Winrun.exe
    • C:\Winnt\Profiles\All Users\Start Menu\Programma's\Opstarten\Winrun.exe
    • C:\Winnt\Profiles\All Users\Start Menu\Programs\Startup\Winrun.exe
    • C:\Winnt\Profiles\User Default\Programma's\Opstarten\Winrun.exe
    • C:\Winnt\Profiles\User Default\Programs\Startup\Winrun.exe
    • C:\Winnt\Profiles\User Default\Start Menu\Programma's\Opstarten\Winrun.exe
    • C:\Winnt\Profiles\User Default\Start Menu\Programs\Startup\Winrun.exe
    • C:\Program Files\Abyss Web Server\Setup\JVM4506.exe
    • C:\Program Files\MyWebServer\Setup\JVM4506.exe
    • A:\.exe

  2. Creates the following files:
    • C:\Program Files\Abyss Web Server\Setup\Index.html (326 bytes)
    • C:\Program Files\Abyss Web Server\Abyss.conf (448 bytes)
    • C:\Program Files\MyWebServer\Mywebserver.ini (1,046 bytes)
    • C:\Program Files\MyWebServer\Setup\Index.html (326 bytes)
    • C:\Program Files\WinMX\Library (54 bytes)
    • C:\Programme\WinMX\library (54 bytes)

      NOTE: These files are not viral by themselves, therefore, Symantec antivirus products do not detect them. Manually delete the files if your system is infected with this worm.

  3. Creates a hidden folder, C:\SharedDocs, and makes many copies of itself into this folder. Some examples of filenames are:
    • Red alert (all versions!) crack.exe
    • Robin Hood -Legend of Sherwood- crack noCD.exe
    • Sex movie hardcore.exe
    • Norton antivirus crack nocd.exe
    • LiveUpdate crack.exe
    • Hardcore SM spanking movie 001.exe
    • Unreal Tournament 2003 crack.exe
    • AOL Hacker password hacker.exe
    • Winur.exe
    • Winrun.exe

  4. Adds the values:

    sysdir C:\winnt\winrun.exe
    windir C:\windows\winrun.exe

    to the registry key:

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

  5. Adds the values:

    winur C:\winnt\winrun.exe
    winrun C:\windows\winrun.exe

    to the registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

    so that the worm runs when you start Windows.
6. If the current system time is 17 minutes of any hour, the worm searches for the .doc files on a floppy disk and copies itself there using the same filename and the .doc.exe double extension.

For example, if the worm finds a file, A.doc, on the floppy, it copies itself as A.doc.exe.


Recommendations

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

  • Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
  • 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.
  • Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
  • Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
  • Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
  • Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
  • If a 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.
  • Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
  • Isolate compromised computers quickly to prevent threats from spreading further. 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.
  • If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
  • For further information on the terms used in this document, please refer to the Security Response glossary.

Writeup By: Yana Liu

Discovered: March 21, 2003
Updated: February 13, 2007 11:45:01 AM
Type: Worm
Systems Affected: Windows


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

  1. Update the virus definitions.
  2. Run a full system scan and delete all the files detected as W32.HLLW.Winur.B. Manually delete the following files if they exist:
    • C:\Program Files\Abyss Web Server\Setup\Index.html
    • C:\Program Files\Abyss Web Server\Abyss.conf
    • C:\Program Files\MyWebServer\Mywebserver.ini
    • C:\Program Files\MyWebServer\Setup\Index.html
    • C:\Program Files\WinMX\Library
    • C:\Programme\WinMX\Library

3. Reverse the changes that the worm made to the registry.

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

1. Updating 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: These virus definitions are posted to the LiveUpdate servers once each week (usually on Wednesdays), unless there is a major virus outbreak. To determine whether definitions for this threat are available by LiveUpdate, refer to the Virus Definitions (LiveUpdate).
  • Downloading the definitions using the Intelligent Updater: The Intelligent Updater virus definitions are posted on U.S. business days (Monday through Friday). 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 the Virus Definitions (Intelligent Updater).

    The Intelligent Updater virus definitions are available here. For detailed instructions on how to download and install the Intelligent Updater virus definitions from the Symantec Security Response Web site, click here.

2. Scanning for and deleting the infected files
  1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
  2. Run a full system scan.
  3. If any files are detected as infected with W32.HLLW.Winur.B, click Delete.
  4. Using Windows Explorer, find and delete the following files:
    • C:\Program Files\Abyss Web Server\Setup\Index.html
    • C:\Program Files\Abyss Web Server\Abyss.conf
    • C:\Program Files\MyWebServer\Mywebserver.ini
    • C:\Program Files\MyWebServer\Setup\Index.html
    • C:\Program Files\WinMX\Library
    • C:\Programme\WinMX\Library
3. Reversing the changes made to the registry

CAUTION : Symantec strongly recommends that you back up the registry before you make any changes to it. Incorrect changes to the registry can result in permanent data loss or corrupted files. Modify the specified keys only. Read the document, "How to make a backup of the Windows registry ," for instructions.
  1. Click Start, and then click Run. (The Run dialog box appears.)
  2. Type regedit, and then click OK. (The Registry Editor opens.)
  3. Navigate to the key:

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
  4. In the right pane, delete the values:

    sysdir C:\winnt\winrun.exe
    windir C:\windows\winrun.exe
  5. Navigate to the key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
  6. In the right pane, delete the values:

    winur C:\winnt\winrun.exe
    winrun C:\windows\winrun.exe
  7. Exit the Registry Editor.


Writeup By: Yana Liu