W32.Babybear@mm

Printer Friendly Page

Discovered: July 23, 2003
Updated: February 13, 2007 12:04:06 PM
Type: Worm
Systems Affected: Windows


W32.Babybear@mm is a worm written in Visual Basic. It spreads using email. Once activated, this worm damages the installations of Symantec antivirus products and may prevent them from running.

W32.Babybear@mm copies itself all over the system and creates many empty folders.



List of folders that are copied to the C drive:
C:\$nProgram Files\System
C:\2Coding7
C:\2Program Files\System
C:\3Coding51
C:\C2oding1
C:\C4oding67
C:\Cchoding74
C:\cCoding55
C:\cCoding67
C:\Ccoding74
C:\Ccodinllg74
C:\cCodlling67
C:\cCoduuing55
C:\Cczhoding74
C:\chCoding67
C:\Cjroding466
C:\Cnoding1
C:\Co2ding2
C:\Co4ding74
C:\Cod2ing3
C:\Codi2ng4
C:\Codi3ng11
C:\Codin2g5
C:\Codin3g23
C:\Codincg11
C:\Codincg23
C:\Codincgkk23
C:\Codincguu11
C:\Codinchg11
C:\Codincyg23
C:\Codinczyg23
C:\Coding1
C:\Coding11
C:\Coding12
C:\Coding142
C:\Coding17
C:\Coding2
C:\Coding23
C:\Coding23j
C:\Coding26
C:\Coding2c3
C:\Coding2ch3
C:\Coding3
C:\Coding31
C:\Coding331
C:\Coding4
C:\Coding411
C:\Coding42
C:\Coding432
C:\Coding44
C:\Coding44c
C:\Coding44j
C:\Coding466
C:\Coding4c2
C:\Coding4cy2
C:\Coding4czy2
C:\Coding4t4
C:\Coding5
C:\Coding51
C:\Coding51c
C:\Coding55
C:\Coding55t
C:\Coding5r1
C:\Coding6
C:\Coding67
C:\Coding67r
C:\Coding7
C:\Coding74
C:\Coding7n
C:\Coding7xn
C:\Codingc12
C:\Codingc12uu
C:\Codingc31
C:\Codingc31kk
C:\Codingch12
C:\Codingcy31
C:\Codingczy31
C:\Codingd2
C:\Codingd2yy
C:\Codingf1
C:\Codingn6
C:\Codingr42
C:\Codings3
C:\Codings4
C:\Codingsy4
C:\Codingt23
C:\Codingxn6
C:\Codingys3
C:\Codingyyf1
C:\Codinkkcg11
C:\Codinng4
C:\Codinng5
C:\Codinrg31
C:\Codintg12
C:\Codinxng5
C:\Codinycg11
C:\Codinygd2
C:\Codinzg466
C:\Codinzycg11
C:\Codinzzg67r
C:\Codirng23
C:\Codirng2xx3
C:\Coditng11
C:\Codixnng4
C:\Codiyngf1
C:\Codiyyng17
C:\Codizng55t
C:\Codizngsy4
C:\Codning3
C:\Codring11
C:\Codrinxxg11
C:\Codsing5
C:\Codsing5y
C:\Codsing6
C:\Codsinjjg6
C:\Codsizng5y
C:\Codsjjing5
C:\Codxning3
C:\Codzing4t4
C:\Codzingys3
C:\Codzzing5r1
C:\Cojjdings4
C:\Cojrding17
C:\Collding51c
C:\Conding2
C:\Cording17
C:\Cording1uu7
C:\Couuding44c
C:\Coxnding2
C:\Coyyding466
C:\Cozdingt23
C:\Cozdinygd2
C:\Croding466
C:\Crodinuug466
C:\Csoding7
C:\Csoding7jj
C:\Cysoding7
C:\Cysodinzg7
C:\czhCoding67
C:\Czodintg12
C:\Czodiyngf1
C:\Czzodingr42
C:\H2elp
C:\hCoding51cy
C:\hCoding51zcy
C:\Hechlp8
C:\Heclp8
C:\Heczhlp8
C:\Hel4p8
C:\Heljrp1
C:\Help
C:\Help1
C:\Help8
C:\Helrp1
C:\Helrp1uf
C:\Heslp
C:\Heyslp
C:\Hezyslp
C:\Hlueclp8
C:\Htelp8
C:\Htelpz8
C:\Hyelp1
C:\jcCoding55
C:\jjCodings3
C:\kkHeslp
C:\llCoding4c2
C:\nProgram Files\System
C:\Pro3gram Files\System1
C:\Progchra1m Files\System
C:\Progcra1m Files\System
C:\Progcuura1m Files\System
C:\Progdram Files\System1
C:\Progr4a1m Files\System
C:\Progra1m Files\System
C:\Program Files\System
C:\Program Files\System1
C:\Progrgam Files\System
C:\Progydram Files\System1
C:\Progyyrgam Files\System
C:\Progzydram Files\System1
C:\Prokkgdram Files\System1
C:\Protgra1m Files\System
C:\Protgraz1m Files\System
C:\Proygrgam Files\System
C:\Prrogram Files\System1
C:\Prroxxgram Files\System1
C:\rHelp
C:\tCoding17
C:\tCoding74
C:\tCodinzg17
C:\tCodizngzz74
C:\Th3e Sims
C:\The 2Sims
C:\The 4S1ims
C:\The jr2Sims
C:\The r2Sims
C:\The rddaljflajflkjorjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj2Sims
C:\The S1ims
C:\The Sims
C:\Thec S1ims
C:\Thech S1ims
C:\Theczzh S1ims
C:\Thes Sims
C:\Theuuc S1ims
C:\Theys Sims
C:\Thezys Sims
C:\Thkes Sims
C:\Thte S1ims
C:\Thte Sz1ims
C:\Thye 2Sims
C:\Thye 2Szims
C:\Thyye 2Sims
C:\Trhe Sims
C:\Trxxhe Sims
C:\uuCoding2c3
C:\xxrHelp
C:\yCodsing6
C:\yCodsizng6
C:\yyCoding55
C:\yyHelp1
C:\zCodinrg31
C:\zCoditng1z1
C:\zProygrgam Files\System


Antivirus Protection Dates

  • Initial Rapid Release version July 23, 2003
  • Latest Rapid Release version September 28, 2010 revision 054
  • Initial Daily Certified version July 23, 2003
  • Latest Daily Certified version September 28, 2010 revision 036
  • Initial Weekly Certified release date July 23, 2003

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

Writeup By: Atli Gudmundsson

Discovered: July 23, 2003
Updated: February 13, 2007 12:04:06 PM
Type: Worm
Systems Affected: Windows


W32.Babybear@mm will arrive as an email attachment, which has the following characteristics:

Subject: Please Confirm

Message Body:
Dear Sir or Madame, We have detected that you have placed a Order for Msn8. Before we start your Service please confirm your order. To confirm your order please check the attachement. Thanks, Microsoft Corporation Support

or as:

Subject: File You Requested

Message Body:
Hey Here is the file you wanted

The attachment name varies, but it can be any of the filenames shown in the list in step 1.

When W32.Babybear@mm is executed, it performs the following actions:

  1. Copies itself as the following files. When doing so, if the files already exist, they will be overwritten:
    • C:\Attachment.exe
    • C:\jNotepad.exe
    • C:\kNotepad.exe
    • C:\lNotepad.exe
    • C:\My Shared Folder\Avril vs. Madonna Video.exe
    • C:\My Shared Folder\file manager program.exe
    • C:\My Shared Folder\Modem Booster.exe
    • C:\My Shared Folder\Msn 8 Full.exe
    • C:\My Shared Folder\Norton Anti-Virus 2003 Cracked!.exe
    • C:\My Shared Folder\Virtual Sex.exe
    • C:\My Shared Folder\Windows Xp Home Edition Key Gen.exe
    • C:\My Shared Folder\Windows Xp Home Edition SP1 Serial.exe
    • C:\Njotepad.exe
    • C:\Nkotepad.exe
    • C:\Nlotepad.exe
    • C:\Nojtepad.exe
    • C:\Noktepad.exe
    • C:\Noltepad.exe
    • C:\Noqtepad.exe
    • C:\Nortepad.exe
    • C:\Notejpad.exe
    • C:\Notekpad.exe
    • C:\Notelpad.exe
    • C:\Notepad.exe
    • C:\Notepadj.exe
    • C:\Notepadk.exe
    • C:\Notepadl.exe
    • C:\NotepadQ.exe
    • C:\NotepadW.exe
    • C:\Notepajd.exe
    • C:\Notepakd.exe
    • C:\Notepald.exe
    • C:\NotepaQd.exe
    • C:\NotepaWd.exe
    • C:\Notepjad.exe
    • C:\Notepkad.exe
    • C:\Noteplad.exe
    • C:\NotepQad.exe
    • C:\NotepWad.exe
    • C:\NoteQpad.exe
    • C:\NoteWpad.exe
    • C:\Notjepad.exe
    • C:\Notkepad.exe
    • C:\Notlepad.exe
    • C:\NotQepad.exe
    • C:\Notrepad.exe
    • C:\NotWepad.exe
    • C:\NoWtepad.exe
    • C:\Nqotepad.exe
    • C:\Nrotepad.exe
    • C:\NWotepad.exe
    • C:\qNotepad.exe
    • C:\rNotepad.exe
    • C:\Windows\Defrag.exe
    • C:\Windows\fNotrepad.exe
    • C:\Windows\Notrefpad.exe
    • C:\Windows\Notrepad.erxe
    • C:\Windows\Notrepad.exe
    • C:\Windows\Notrepad.exef
    • C:\Windows\Notrepadg.exe
    • C:\Windows\Notrepadr.exe
    • C:\Windows\Notrepagd.exe
    • C:\Windows\Notrepajd.exe
    • C:\Windows\Notrepard.exe
    • C:\Windows\Notrepatd.exe
    • C:\Windows\Notrerpad.exe
    • C:\Windows\Notretpad.exe
    • C:\Windows\Start Menu\Programs\Startup\Microsoft Corporation.exe
    • C:\Windows\Systefm\Notrepad.exe
    • C:\Windows\Systegfm\Notrepad.exe
    • C:\windows\system\Microsoft.ini
    • C:\Windows\System\Ngotrepad.exe
    • C:\Windows\System\Nhotrepad.exe
    • C:\Windows\System\Nodtrepad.exe
    • C:\Windows\System\Nogtrepad.exe
    • C:\Windows\System\Notrepad.exe
    • C:\Windows\System\Notrepdad.exe
    • C:\Windows\System\Notrtepad.exe
    • C:\Windows\System\Noturepad.exe
    • C:\Windows\System\Nrotrepad.exe
    • C:\Windows\System\Ntotrepad.exe
    • C:\Windows\Welcome.exe
    • C:\Windowsf\Notrepad.exe
    • C:\WNotepad.exe
    • C:\Wscript.exe

  2. Creates over 200 empty folders on the root of the C drive. Refer to the Additional Information section for a completed list of these folders.

    Note: This action will corrupt the systems in which the C drive is an FAT16 partition.

  3. Continuously deletes (while running) all the files with the following extensions:
    .dat
    .inf
    .dll
    .sys
    .exp
    .cat
    .txt
    .vxd

    from the folders:

    C:\Program Files\Common Files\Symantec Shared
    C:\Program Files\Common Files\Symantec Shared\Livereg
    C:\Program Files\Common Files\Symantec Shared\Scriptblocking
    C:\Program Files\Common Files\Symantec Shared\Virusdefs
    C:\Program Files\Common Files\Symantec Shared\Virusdefs\20020227.005
    C:\Program Files\Common Files\Symantec Shared\Virusdefs\20030618.006

    This action may have the effect of disabling many Symantec antivirus products.

  4. Creates the registry values:

    "Msgmgr"=<path to executable of the worm>
    "Microsoft Corporation"=<path to executable of the worm>

    under the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

  5. Displays the messages:

    Title: Application Error

    Message: Missing .Dll File

    and:

    Message:
    <imge with a reference to Bugbear.B>
    with the text:
    From the Creators of BugBear

  6. Sends itself to all the contacts in your Address Book.


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.

Writeup By: Atli Gudmundsson

Discovered: July 23, 2003
Updated: February 13, 2007 12:04:06 PM
Type: Worm
Systems Affected: Windows


The following instructions pertain to all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.

  1. Disable System Restore (Windows Me/XP).
  2. Download virus definitions using the Intelligent Updater, but do not install them.
  3. Restart the computer in Safe mode or end the process.
  4. Run the intelligent Updater.
  5. Run a full system scan and delete all the files detected as W32.Babybear@mm.
  6. Delete the values that were added to the registry.
  7. Delete the empty folders that the worm added.
For specific details on each of these steps, read the following instructions.

1. Disabling System Restore (Windows Me/XP)
If you are running Windows Me or Windows XP, we recommend that you temporarily turn off System Restore. Windows Me/XP uses this feature, which is enabled by default, to restore the files on your computer in case they become damaged. If a virus, worm, or Trojan infects a computer, System Restore may back up the virus, worm, or Trojan on the computer.

Windows prevents outside programs, including antivirus programs, from modifying System Restore. Therefore, antivirus programs or tools cannot remove threats in the System Restore folder. As a result, System Restore has the potential of restoring an infected file on your computer, even after you have cleaned the infected files from all the other locations.

Also, a virus scan may detect a threat in the System Restore folder even though you have removed the threat.

For instructions on how to turn off System Restore, read your Windows documentation, or one of the following articles:
For additional information, and an alternative to disabling Windows Me System Restore, see the Microsoft Knowledge Base article, "Antivirus Tools Cannot Clean Infected Files in the _Restore Folder ," Article ID: Q263455.

2. Downloading the virus definitions
Download the Intelligent Updater virus definitions but do not install them yet. Read "How to update virus definition files using the Intelligent Updater " for detailed instructions.

3. Restarting the computer in Safe mode or ending the worm's process
  • For Windows 95, 98, Me, 2000, or XP users, restart the computer in Safe mode. For instructions, refer to the document, "How to start the computer in Safe Mode."
  • For Windows NT 4 users, you must end the process on the worm's files. This process is more complex. Using the Windows Task manager, end any application or process named "Project1" or anything that appears in the list in Step 1 of the Technical Details section.

4. Running the Intelligent Updater
Double-click the Intelligent Updater file that you downloaded and follow any prompts.

5. Scanning for and deleting the infected files
  1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
  2. Run a full system scan.
  3. If any files are detected as infected with W32.Babybear@mm, click Delete.

6. Deleting the value from the registry

CAUTION : Symantec strongly recommends that you back up the registry before making any changes to it. Incorrect changes to the registry can result in permanent data loss or corrupted files. Modify the specified keys only. Read the document, "How to make a backup of the Windows registry ," for instructions.
  1. Click Start, and then click Run. (The Run dialog box appears.)
  2. Type regedit

    Then click OK. (The Registry Editor opens.)

  3. Navigate to the key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

  4. In the right pane, delete the values:

    "Msgmgr"=<path to executable of the worm>
    "Microsoft Corporation"=<path to executable of the worm>

  5. Exit the Registry Editor.


7. Deleting the empty folders that the worm added
Using Windows Explorer, delete any of the folders shown in the list in the Additional Information section.


Writeup By: Atli Gudmundsson