- 13 February 2001
- 13 February 2007
- Also Known As:
- VBS.San [Computer Associates], VBS/Valentin@MM [McAfee], VBS/San-A [Sophos], VBS_VALENTIN.A [Trend Micro]
- Systems Affected:
VBS.Valentin@mm uses the built-in Encoding function of Visual Basic files. When executed, this virus sends itself to all recipients in the Microsoft Outlook address book. It also spreads using mIRC and by copying itself to shared network drives. The payload overwrites files and adds the .txt extension to them. The payload is executed if the day of the month is the 8th, 14th, 23rd, or the 29th.
Currently Symantec has not received any submissions of this worm.
Antivirus Protection Dates
- Initial Rapid Release version 13 February 2001
- Latest Rapid Release version 28 September 2010 revision 054
- Initial Daily Certified version 13 February 2001
- Latest Daily Certified version 28 September 2010 revision 036
- Initial Weekly Certified release date 13 February 2001
Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.
VBS.Valentin@mm uses the VBScript.Encode function to embed itself within an HTML file.
Upon execution, the virus creates the file Main.html in the \Windows\System folder. It then sends this file to all recipients in the Microsoft Outlook address book. The subject of the email message is left blank. The viral code is contained in HTML form within the email message itself.
This virus also attempts to send email to random cell phone numbers with the following subject and message:
Subject: Feliz san valentin
Message: Feliz san valentin. Por favor visita...
Included in the message is the Web site of the virus creator.
The virus also searches shared network drives for the mIRC program, and if found, creates the Script.ini file in the mIRC folder. This spreads the virus the next time that you sign on to mIRC. The virus searches shared network drives, and if it encounters a shortcut with the .url extension, it replaces the shortcut with a shortcut to the virus creator's Web site.
When the day of the month is the 8th, 14th, 23rd, or 29th, the virus overwrites files with a text file that contains the following:
Hola, me llamo Onel2 y voy a utilizar tus archivos para declararle mi amor
a Davinia, la chica mas guapa del mundo.
Feliz san Valentin Davinia. Eres la mas bonita y la mas simpatica.
Todos los dias a todas horas pienso en ti y cada segundo que no te veo
es un infierno.
Quieres salir conmigo?
En cuanto a ti usuario, debo decirte que tus ficheros
no han sido contaminados por un virus,
sino sacralizados por el amor que siento por Davinia.
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 recover from this infection:
- Run LiveUpdate to make sure that you have the most recent virus definitions.
- Start Norton AntiVirus (NAV), and run a full system scan, making sure that NAV is set to scan all files.
- If any files are found to be infected by VBS.Valentin@mm, delete them.
- Do one of the following:
- If you use mIRC and the virus has overwritten the Script.ini file, replace the file from a backup or reinstall the program.
- If you do not use mIRC, but it is installed on the computer, as a precaution use Windows Explorer to delete the Script.ini file.