- 22 March 2002
- 13 February 2007
VBS.Krim@mm is a Visual Basic Script (VBS) worm that uses Microsoft Outlook MAPI to mail itself to all contacts in the Outlook address book.
Antivirus Protection Dates
- Initial Rapid Release version 25 March 2002
- Latest Rapid Release version 28 September 2010 revision 054
- Initial Daily Certified version 25 March 2002
- Latest Daily Certified version 28 September 2010 revision 036
- Initial Weekly Certified release date 27 March 2002
Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.
VBS.Krim@mm arrives as an email attachment. The email has the following characteristics:
Message: Che stai facendo ????
This attachment is a batch file. When it is executed, it does the following:
It creates the folder C:\Windows\Mk
It creates the following files:
The worm then copies itself as C:\Windows\Mk\Mirko.bat.
Next, it appends the following line to the end of the C:\Autoexec.bat file:
The worm then attempts to add the value
to the registry key
The worm then searches for the file C:\Windows\Desktop\Mirko.txt. If the worm cannot find this file on the desktop, it begins to perform a quick format of drive C.
Next, the worm uses the file C:\Windows\Mirko.vbs to mail itself to all contacts in Outlook address book.
Finally, it uses C:\Windows\Mk\Mirko.vbs to display the following message:
- Norton AntiVirus detects both C:\Windows\Mk\Mirko.bat and C:\Windows\Mirko.vbs as VBS.Krim@mm.
- It does not detect C:\Windows\Mk\Mirko.vbs, C:\Windows\Mirko.reg, or C:\Windows\Desktop\Mirko.txt because they are not viral.
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.
Delete any files detected as VBS.Krim@mm, remove the value that it added to the registry, and (on Windows 95/98/Me computers) remove the line that it added to the Autoexec.bat file.
To remove this worm:
- Obtain the most recent virus definitions. There are two ways to do this:
- Run LiveUpdate. LiveUpdate is the easiest way to obtain virus definitions. These virus definitions have undergone full quality assurance testing by Symantec Security Response and are posted to the LiveUpdate servers one time each week (usually Wednesdays) unless there is a major virus outbreak. To determine whether definitions for this threat are available by LiveUpdate, look at the Virus Definitions (LiveUpdate) line at the top of this write-up.
- Download the definitions using the Intelligent Updater. Intelligent Updater virus definitions have undergone full quality assurance testing by Symantec Security Response. They are posted on U.S. business days (Monday through Friday). They must be downloaded from the Symantec Security Response Web site and installed manually. To determine whether definitions for this threat are available by the Intelligent Updater, look at the Virus Definitions (Intelligent Updater) line at the top of this write-up.
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.
- Start Norton AntiVirus (NAV), and make sure that NAV is configured to scan all files. For instructions on how to do this, read the document How to configure Norton AntiVirus to scan all files.
- Run a full system scan.
- Delete all files that are detected as VBS.Krim@mm.
- Using Windows Explorer, delete C:\Windows\Mk\Mirko.vbs, C:\Windows\Mirko.reg, and C:\Windows\Desktop\Mirko.txt.
To edit the registry:
CAUTION : We strongly recommend 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 only the keys that are specified. Read the document How to make a backup of the Windows registry for instructions.
- Click Start, and click Run. The Run dialog box appears.
- Type regedit and then click OK. The Registry Editor opens.
- Navigate to the following key:
- In the right pane, delete the following value:
- Click Registry, and click Exit.
To edit the Autoexec.bat file:
This is necessary only on Windows 95/98/Me-based computers.
NOTE: (For Windows Me users only) Due to the file-protection process in Windows Me, a backup copy of the file that you are about to edit exists in the C:\Windows\Recent folder. We recommend that you delete this file before you continue with the steps in this section. To do this using Windows Explorer, go to the C:\Windows\Recent folder, and in the right pane select and delete the Win.ini file. It will be regenerated as a copy of the file that you are about to edit when you save your changes to that file.
- Click Start, and click Run.
- Type the following, and then click OK.
The MS-DOS Editor opens.
- Delete the following line:
- Click File, and click Save.
- Click File, and click Exit.