VBS.Waterworks.Worm

When VBS.Waterworks.Worm runs, it does the following:

1. Creates copies of itself as:
   • %System%\BootLoader.exe.vbs
   • Win32 Strt.exe.vbs (Normally, this is at C:\Win32 Strt.exe.vbs, but the file is created in the root of the default drive. The intention was to create this file as %Windir%\Win32 Strt.exe.vbs, but this does not always work due to bugs in the worm's code.)
   • %Windir%\Jokes.htm. This is an HTML version of the worm.
   • %Windir%\Winupdate.exe. This is an mIRC INI script.
     
     
2. Overwrites these existing files with a copy of itself:
   • %Windir%\Readme.htm. (This is an HTML version of the worm.)
   • %Windir%\Htmlhelp.htm. (This is an HTML version of the worm.)
   • %System%\Winhelp32.exe. (This is an HTML version of the worm.)
   • %Mirc%\script.ini (mIRC INI script)
     
     NOTES:
     • %Windir% is a variable. The worm locates the Windows installation folder (by default, this is C:\Windows or C:\Winnt) and copies the files to that location.
     • %System% is a variable. The worm locates the System folder and copies the files 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).
     • %Mirc% is a variable. The worm locates the mIRC installation folder (by default this is C:\Mirc or C:\Mirc32) and copies the files to that location.
       
       
3. Adds the value:
   
   BootLoader C:\WINDOWS\SYSTEM\BootLoader.exe.vbs
   
   to the registry key:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
   
   so that the worm runs when you start Windows.
   
4. Adds the value:
   
   Win32 Strt.EXE \Win32 Strt.exe.vbs (or %windir%\Win32 Strt.exe.vbs)
   
   to the registry key:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
   
   so that the worm runs when you start Windows.
   
5. Spreads to all the local and mapped drives. Files with the .vbs extension, .VBS, are replaced with a copy of the worm's .vbs file. Files that have the extensions .htm, .html, .asp, .htx, and .hta are replaced with the .HTML version of the worm.
   
   If the HTML code is executed, the worm is dropped as %System%\Update.vbs. This may be a feature intended for future use to update the worm's code from the Internet.
   
   The mIRC INI script, which the worm drops, is used to send the %Windir%\Jokes.htm file to anyone who joins the same channel as the infected computer.

Payload

The worm activates its payload on three different days, as shown here:

Day	Message box title	Message box text
October 15	my b-day	happy birthday kefi
November 23	11/23!	holy sh*t! it's 11/23
December 25	kefi [rRlf]	Organized religion controls the world.

On these payload activation days, the worm also creates 16 text files in your Startup folder. The file name uses the format: Startup\Evion(n).txt, where n is between 0 and 15 (inclusive). These files have 50 lines of randomly generated text that is selected from these three lines:

You've done and gotten your self infected with Vbs.Evion by kefi [rRlf]
[rRlf] ownz joo bitch
Catfish_VX are lamers. This virus was constructed for them to steal

The next time you log in, these random text messages will be displayed using the default text program, usually in Notepad.

Other indications
On days other than the ones on which the payload runs, a text document will be created on the Windows desktop. The file name uses the format "Desktop\%day% - %month%.vir.txt".

For example, on February 5th, the file would be Desktop\5 - 2.vir.txt.

The message inside this text file is:

today you did not experience the payload of Vbs.Evion
sorry..

kefi [rRlf]

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.

Summary