VBS.Keinef

1. Modifies the Value Data of the (Default) value in the registry key:
   
   HKEY_CLASSES_ROOT\exefile\shell\open\command
   
   to:
   
   "\Windows\wscript.exe" "" "%1" "%*
   
   This will prevent you from running the .exe files.
   
2. Modifies the Value Data of the (Default) value in the registry key:
   
   HKEY_CLASSES_ROOT\comfile\shell\open\command
   
   "\Windows\wscript.exe" "" "%1" "%*"
   
   This will prevent you from running the .com files.
   

1. Checks the system date. If the date is the 24th of any month, VBS.Keinef writes a Java Applet Class named "AppletSpamming.class" and adds it to the file \Windows\Spoofing.htm.
2. Opens Spoofing.htm in Internet Explorer. However, this action is hidden, and you will not see the Spoofing.htm file when it is opened.
3. Displays the message:
   
   
   
4. Copies itself to all the network drivers as Klm#.vbs.
5. Modifies the \Windows\Win.ini file on all the network drives by adding the text:
   
   run=c:\klm#.vbs
   
   This causes the Klm#.vbs file to run when you start Windows.
   
   NOTE: The file name Klm#.vbs will vary. The # is a random number.

1. Searches for files in the \Windows folder with the string "PWL" in the file name and adds these files to a list.
2. Sends all the files in the list it created as email attachments. The format of the email message is:
   
   Recipients: ovg_psws@hotmail.com
   Subject: Password
   Message: The message consist of the this information:
   
   Computer name, User name, User domain, Registered Organization, Registered Owner, Platform type
   
   Attachment: The files that VBS.Keinef found in step 1.

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.