- 29 December 1999
- 13 February 2007
- Also Known As:
Antivirus Protection Dates
- Initial Rapid Release version 30 December 1999
- Latest Rapid Release version 28 September 2010 revision 054
- Initial Daily Certified version 30 December 1999
- Latest Daily Certified version 28 September 2010 revision 036
- Initial Weekly Certified release date pending
Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.
The Windows Scripting Host (WSH) is required for this worm to replicate. The WSH is packaged with Windows 98/2000/NT and Internet Explorer 5.0, or it can be downloaded from Microsoft's Web site and installed in Windows 95. This Visual Basic Script worm begins by copying itself to the following locations:
Next, the worm adds the following registry keys to ensure that it is executed each time the system is restarted:
Then, the worm identifies each of the drives to which the infected computer is attached and copies itself to the root directory of all fixed and network drives.
If Microsoft Outlook is installed, the worm first checks for the existence of the following registry key:
If the key does not exist, it is created. Then the worm attempts to mail itself to each entry in the address book with the following information:
Subject: Please Read
Body: Hey, you really need to check out this
attached file I sent you...please check it
out as soon as possible.
The email message also contains the attachment Tune.vbs.
If mIRC is installed on the target computer in the default folder of C:\Mirc, then the virus modifies C:\Mirc\Script.ini and C:\Mirc\Mirc.ini so that each time an IRC user joins the infected user's channel, a copy of Tune.vbs is sent by DCC. Similarly, if Pirch98 is installed on the target computer in C:\Pirch98, the virus modifies C:\Pirch98\Events.ini and C:\Pirch98\Pirch98.ini, so that each time an IRC user joins the infected user's channel, a copy of Tune.vbs is sent by DCC.
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.
To repair damage done by VBS.Tune:
- Run a full system scan, and delete any infected files. Do a full shutdown of the computer, and then restart.
- Delete any values that are loading from the registry's \Run key that refer to Tune.vbs
- Remove references to Tune.vbs from the Run= and Load= lines of the Win.ini file.
- Remove references to Tune.vbs from the Shell= line of the System.ini file
For detailed instructions on how to do this, see the sections that follow.
NOTE: The procedure described in this document is somewhat complex. It is assumed that you are familiar with basic Windows and DOS procedures. If you are not, then we suggest that you obtain the services of a qualified computer consultant.
Run a full system scan
After making sure that you have current virus definitions, run a full system scan. Make sure that Norton AntiVirus is set to scan all files. Delete any files that are found to be infected.
When the scan has finished, exit all programs, shut down the computer, and then turn off the power. Leave the computer off for at least thirty seconds. This is necessary to clear memory. Do not use the reset button or perform a normal restart from Windows.
NOTE: You will likely see error messages when Windows restarts. Click OK or Ignore as needed.
Edit the registry
You must remove the values that were added to the Windows registry by the worm. Follow these steps to do this:
CAUTION : We strongly recommend that you back up the system registry before making any changes to it. Incorrect changes to the registry may result in permanent data loss or corrupted files. Be sure to modify the specified keys only. See the document How to back up the Windows registry before proceeding.
To edit the registry:
- Click Start, and click Run. The Run dialog box appears.
- Type regedit and then click OK. The Registry Editor opens.
- Navigate to and select the following subkey:
- In the right pane, look for any values that refer to Tune.vbs. These may have Tune.vbs as part of the value, or they may be displayed as one or both of the following:
- If any of these are found, then select them, press Delete, and click Yes to confirm.
- Click the Registry menu, and click Exit to save the changes and exit the Registry Editor.
To edit system files
This worm also makes changes to two system files. Follow these steps to remove the changes:
- Click Start, and click Run.
- Type sysedit and then click OK. The System Configuration Editor appears.
- Click the Window menu and click C:\WINDOWS\WIN.INI. The Win.ini window is brought to the front.
NOTE: This menu item may appear slightly different if Windows is installed in a different location.
- In the [windows] section at the beginning of the file, look for the following lines:
- On both lines, look for references to Tune.vbs. If found, carefully delete these references. Make sure that you delete only these references, and not the lines that follow.
- Click the Window menu, and click C:\WINDOWS\SYSTEM.INI. The System.ini window is brought to the front.
- In the [boot] section at the beginning of the file, look for the line that begins with:
- Look for an additional reference that has been added to it. It may appear similar to the following:
- Remove the reference to Explorer.vbs. When you are finished the line must appear as follows:
- Click the File menu, and click Save.
- Exit the System Configuration Editor.
This completes the removal of the worm. Run another full system scan.