1. Symantec/
  2. Security Response/
  3. W32.Randex


Risk Level 1: Very Low

June 4, 2003
February 13, 2007 12:25:39 PM
Systems Affected:

When W32.Randex is executed, it does the following:
  1. Copies itself to the %System% folder.

    : %System% is a variable. The worm locates the System folder and copies itself to that location. By default, this is C:\Windows\System (Windows 95/98/Me), C:\Winnt\System32 (Windows NT/2000), or C:\Windows\System32 (Windows XP).

  2. Calculates a random IP address for a computer to infect.

  3. Attempts to authenticate itself to the IP addresses using weak passwords.

    For example:
    • pass
    • password
    • computer
    • 12345

  4. If successful, the worm copies itself as:
    • ipc$
    • C$
    • Admin$

  5. Schedules a Network Job to run the worm.

  6. Can be configured to perform Denial of Service (DoS) attacks on specified servers.

  7. Can be configured to terminate security product processes.

  8. Connects to specified IRC servers and joins a channel to receive commands.

  9. Adds a variable registry value to one or more of the following registry keys:





    For example:

    "superslut" = "msslut32.exe"

  10. May steal the CD keys of games, such as:

    Battlefield 1942 The Road to Rome
    Battlefield 1942 Secret Weapons of WWII
    Unreal Tournament 2003
    Found Half-Life

  11. May send personal information, such as the operating system, IP address, user name, and so on, to the IRC server.

  12. May open a backdoor port.

  13. May download the file from the Internet and update itself.

  14. May spread by exploiting the following vulnerabilities:


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: Kaoru Hayashi
Summary| Technical Details| Removal

Search Threats

Search by name
Example: W32.Beagle.AG@mm
STAR Antimalware Protection Technologies
2016 Internet Security Threat Report, Volume 21
  • Twitter
  • Facebook
  • LinkedIn
  • Google+
  • YouTube