W32.HLLW.Ultimax

Risk Level 2: Low

Printer Friendly Page

Discovered: July 16, 2002
Updated: February 13, 2007 11:39:46 AM
Also Known As: W32.Ultimax.Worm, Win32.Ultimax.A [CA], W32/Ultimax.Worm [McAfee], TROJ_ULTIMAX.A [Trend], TrojanDownloader.Win32.Ultimx.
Type: Worm
Systems Affected: Windows 2000, Windows 98, Windows Me, Windows NT, Windows XP


When W32.HLLW.Ultimax is first executed, it copies itself as C:\%windir%\Rdvs.exe, or C:\%System%\<original file name>, depending on the variant.

NOTES:
  • %windir% is a variable. The worm locates the Windows main installation folder (by default this is C:\Windows or C:\Winnt) and may copy itself to that location.
  • %System% is a variable. The worm locates the Windows System folder (by default this is C:\Windows\System or C:\Winnt\System32) and may copy itself to that location.
  • Variations on the file name that it copies itself as have been reported, for example, C:\%windir%\Rdve.exe.

It then downloads and runs a file that gives access to a pornographic service.

The worm attempts to connect to random IP addresses, and it searches shares to find the %windir% folder on remote computers.

If the worm finds the %windir% folder, it then uses various language-dependent variations of the %startup% folder to attempt to guess the name of the %startup% folder and copy itself to that location.

If it is successful, then when the computer is restarted, the worm creates one of the following values (depending on the variant):

fn

or,

rdvs C:\%System%\<the worm file name>

in the registry key

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

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: Peter Ferrie
Search by name
Example: W32.Beagle.AG@mm
Windows 7
Windows Vista Security