Printer Friendly Page

Discovered: June 08, 2001
Updated: February 13, 2007 11:54:25 AM
Also Known As: VBS.Pando, VBS/Pando
Type: Virus

VBS.Pando.A is an overwriting Visual Basic script (VBS) virus. It searches for .vbs files in the current folder (the location of the viral script), the parent folder of the current folder, and the \Windows folder; it then copies itself over these files. The script also creates the file Startup.lnk in the StartUp folder. This shortcut ensures that the viral script is executed every time that Windows starts.

If the current minute is :09 when the script is executed, a message will appear.

Antivirus Protection Dates

  • Initial Rapid Release version June 08, 2001
  • Latest Rapid Release version August 08, 2016 revision 023
  • Initial Daily Certified version June 08, 2001
  • Latest Daily Certified version August 09, 2016 revision 001

Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

Writeup By: Brian Ewell

Discovered: June 08, 2001
Updated: February 13, 2007 11:54:25 AM
Also Known As: VBS.Pando, VBS/Pando
Type: Virus

This Visual Basic script searches the following locations for .vbs files:

  • The current folder from which the script was executed
  • The parent folder of the folder that contains the script
  • The \Windows folder

If any .vbs files are found in these locations (this does not include subfolders of those folders) they will be overwritten by a copy of the script. Such files cannot be repaired and must be deleted.

The script also creates a shortcut in the StartUp folder named Startup.lnk. This shortcut runs the file Ultras.vbs every time that Windows starts.

The following message appears if the script is executed while the current minute is :09:


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: Brian Ewell

Discovered: June 08, 2001
Updated: February 13, 2007 11:54:25 AM
Also Known As: VBS.Pando, VBS/Pando
Type: Virus

  1. Run LiveUpdate to make sure that you have the most recent virus definitions.
  2. Start Norton AntiVirus (NAV), and run a full system scan, making sure that NAV is set to scan all files.
  3. Files detected as VBS.Pando.A should be deleted and restored from backup, if necessary.
  4. Delete Startup.lnk from the StartUp folder.

Writeup By: Brian Ewell