1. Symantec/
  2. Security Response/
  3. VBS.Davinia.B


Risk Level 1: Very Low

February 7, 2001
February 13, 2007 11:53:30 AM
Worm, Macro

The worm arrives as an HTML email message. The subject and the body appear blank. The worm can only properly operate if you are using Microsoft Outlook without the Office 2000 UA Control patch. When reading the message, the HTML code will launch Internet Explorer. Internet Explorer will attempt to download and open a Word 2000 document.

The Word 2000 document contains a macro, which does the following:
  1. Creates the \Windows\System\Littledavinia.vbs file.
  2. Adds the value:

    Davinia         \Windows\System\Littledavinia.vbs

    to the following registry key:


    This causes the file to be run when Windows starts.
  3. The macro sends an HTML email message to all contacts in the Microsoft Outlook address book. This is recorded in the registry so that they are not emailed again.
  4. The next time that the computer is restarted, the VBS file is executed. The VBS file first modifies the start page of Internet Explorer.
  5. It then adds the value:

    Davi        littledavinia.html

    to the following key:

  6. The worm searches for all files on local and mapped drives and overwrites the files with HTML code. The HTML code displays a message that is customized with your name and email address.
  7. The worm also creates the file \Windows\System\Littledavinia.html with the same code. This is executed the next time Windows is restarted.


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: Douglas Knowles
Summary| Technical Details| Removal

Search Threats

Search by name
Example: W32.Beagle.AG@mm
STAR Antimalware Protection Technologies
2016 Internet Security Threat Report, Volume 21
  • Twitter
  • Facebook
  • LinkedIn
  • Google+
  • YouTube