Threat Explorer

The Threat Explorer is a comprehensive resource consumers can turn to for daily, accurate, up-to-date information on the latest threats, risks and vulnerabilities.



29 March 2001
13 February 2007
Also Known As:

VBS.Breberka.A@mm is an encrypted .vbe worm that sends itself as an attachment to all users in all MAPI address books. The message is:

Subject: IQ Test!!!
Message: r u stupid? [Y/N] ;)))
Attachment: Breberka.txt<10 blank spaces>.vbe

It also attempts to connect to fixed and network drives in an effort to replicate.

Antivirus Protection Dates

  • Initial Rapid Release version 03 April 2001
  • Latest Rapid Release version 08 August 2016 revision 023
  • Initial Daily Certified version 03 April 2001
  • Latest Daily Certified version 09 August 2016 revision 001
  • Initial Weekly Certified release date pending
Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

When executed, VBS.Breberka.A@mm does the following:
  1. This worm checks for the existence of the following registry key before attempting to activate its payloads:


    with a value of: gl

  2. If this registry key does not exist, the worm creates a copy of itself in the current Windows folder as Winhelp.vbe and in the current Windows temporary folder as Breberka.txt[10 spaces].vbe.
  3. It then mails to all entries in all MAPI address books and creates the \Breberka registry key to prevent future activation.
  4. The value:

    SysHelp / StartUp     C:\Windows\winhelp.vbe

    is added to the registry key


    This ensures that the worm is run when Windows starts.
  5. Next, the worm attempts to connect to all fixed and network drives, and creates two files in the root folders of these drives:
    • A 16-byte file named
    • A copy of the worm named Breberka.txt<10 spaces>.vbe
  6. Finally, the worm attempts to modify any file named Autoexec.bat that is found on any of the drives, so that is run when Windows starts.


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 remove this worm, delete files detected as VBS.Breberka.A@mm, and then remove the entries added to the registry.

To remove the worm:
  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. Delete any files detected as VBS.Breberka.A@mm.

To edit the registry:

CAUTION : We strongly recommend that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure you modify only the keys specified. Please see the document How to back up the Windows registry before proceeding.
  1. Click Start, and click Run. The Run dialog box appears.
  2. Type regedit and then click OK. The Registry Editor opens.
  3. Navigate to the following key:

  4. In the right pane, delete the following value: gl
  5. Navigate to the following key:

  6. In the right pane, delete the following value:

    SysHelp / StartUp     C:\Windows\winhelp.vbe
  7. Click Registry, and click Exit to save the changes.

Writeup By: SARC Engineer