W32.Mockbot.A.Worm

Printer Friendly Page

Discovered: February 25, 2004
Updated: February 13, 2007 12:18:57 PM
Type: Worm
Systems Affected: Windows



W32.Mockbot.A.Worm is a worm that spreads using computers infected with the W32.Mydoom.A@mm , and Backdoor.Optix worms. To spread itself, the worm can also exploit the DCOM RPC vulnerability (described in Microsoft Security Bulletin MS03-026 ), as well as a vulnerability in the DameWare Mini Remote Control program.

W32.Mockbot.A.Worm is written in C and is packed with UPX.



The list of monitored processes:

  • _AVP32.EXE
  • _AVPCC.EXE
  • _AVPM.EXE
  • AckWin32.EXE
  • ACKWIN32.EXE
  • ADVXDWIN.EXE
  • AGENTSVR.EXE
  • agentw.EXE
  • ALERTSVC.EXE
  • ALOGSERV.EXE
  • AMON9X.EXE
  • ANTI-TROJAN.EXE
  • ANTIVIRUS.EXE
  • ANTS.EXE
  • APIMONITOR.EXE
  • APLICA32.EXE
  • apvxdwin.EXE
  • APVXDWIN.EXE
  • ATCON.EXE
  • ATGUARD.EXE
  • ATRO55EN.EXE
  • ATUPDATER.EXE
  • ATWATCH.EXE
  • AUPDATE.EXE
  • AUTODOWN.EXE
  • AutoTrace.EXE
  • AUTOUPDATE.EXE
  • AVCONSOL.EXE
  • AVE32.EXE
  • AVGCC32.EXE
  • Avgctrl.EXE
  • AVGCTRL.EXE
  • AVGNT.EXE
  • AvgServ.EXE
  • AVGSERV.EXE
  • AVGSERV9.EXE
  • AVGUARD.EXE
  • AVGW.EXE
  • avkpop.EXE
  • AvkServ.EXE
  • avkservice.EXE
  • avkwctl9.EXE
  • AVNT.EXE
  • AVP.EXE
  • AVP32.EXE
  • AVPCC.EXE
  • AVPDOS32.EXE
  • avpm.EXE
  • AVPM.EXE
  • AVPTC32.EXE
  • AVPUPD.EXE
  • Avsched32.EXE
  • AvSynMgr.AVSYNMGR.EXE
  • AVWIN95.EXE
  • AVWINNT.EXE
  • AVWUPD32.EXE
  • AVWUPSRV.EXE
  • AVXMONITOR9X.EXE
  • AVXMONITORNT.EXE
  • AVXQUAR.EXE
  • BD_PROFESSIONAL.EXE
  • BIDEF.EXE
  • BIDSERVER.EXE
  • BIPCP.EXE
  • BIPCPEVALSETUP.EXE
  • BISP.EXE
  • blackd.EXE
  • BLACKD.EXE
  • BlackICE.EXE
  • BLACKICE.EXE
  • BOOTWARN.EXE
  • BORG2.EXE
  • bot.exe
  • BS120.EXE
  • ccApp.EXE
  • ccEvtMgr.EXE
  • ccPxySvc.EXE
  • CDP.EXE
  • CFGWIZ.EXE
  • CFIADMIN.EXE
  • CFIAUDIT.EXE
  • CFINET.EXE
  • CFINET32.EXE
  • Claw95.EXE
  • Claw95cf.EXE
  • CLAW95CF.EXE
  • CLEAN.EXE
  • cleaner.EXE
  • CLEANER.EXE
  • cleaner3.EXE
  • CLEANER3.EXE
  • CLEANPC.EXE
  • CMGRDIAN.EXE
  • CMON016.EXE
  • CONNECTIONMONITOR.EXE
  • cpd.EXE
  • CPD.EXE
  • CPF9X206.EXE
  • CPFNT206.EXE
  • CTRL.EXE
  • CV.EXE
  • CWNB181.EXE
  • CWNTDWMO.EXE
  • dcomx.exe
  • defalert.EXE
  • defscangui.EXE
  • DEFWATCH.EXE
  • DEPUTY.EXE
  • dllhost.exe
  • DOORS.EXE
  • DPF.EXE
  • DPFSETUP.EXE
  • DRWATSON.EXE
  • DRWEB32.EXE
  • DVP95.EXE
  • DVP95_0.EXE
  • ECENGINE.EXE
  • EFPEADM.EXE
  • enbiei.exe
  • ENT.EXE
  • ESAFE.EXE
  • ESCANH95.EXE
  • ESCANHNT.EXE
  • ESCANV95.EXE
  • ESPWATCH.EXE
  • ETRUSTCIPE.EXE
  • EVPN.EXE
  • EXANTIVIRUS-CNET.EXE
  • EXE.AVXW.EXE
  • EXPERT.EXE
  • F-AGNT95.EXE
  • fameh32.EXE
  • FAST.EXE
  • fch32.EXE
  • fih32.EXE
  • FINDVIRU.EXE
  • FIREWALL.EXE
  • FLOWPROTECTOR.EXE
  • fnrb32.EXE
  • FPROT.EXE
  • F-PROT.EXE
  • F-PROT95.EXE
  • FP-WIN.EXE
  • FP-WIN_TRIAL.EXE
  • FRW.EXE
  • fsaa.EXE
  • FSAV.EXE
  • fsav32.EXE
  • FSAV530STBYB.EXE
  • FSAV530WTBYB.EXE
  • FSAV95.EXE
  • fsgk32.EXE
  • fsm32.EXE
  • fsma32.EXE
  • fsmb32.EXE
  • f-stopw.EXE
  • F-STOPW.EXE
  • gbmenu.EXE
  • GBMENU.EXE
  • gbpoll.EXE
  • GBPOLL.EXE
  • GENERICS.EXE
  • GUARD.EXE
  • GUARDDOG.EXE
  • HACKTRACERSETUP.EXE
  • HTLOG.EXE
  • HWPE.EXE
  • iamapp.EXE
  • IAMAPP.EXE
  • iamserv.EXE
  • IAMSERV.EXE
  • IAMSTATS.EXE
  • IBMASN.EXE
  • IBMAVSP.EXE
  • ICLOAD95.EXE
  • ICLOADNT.EXE
  • ICMON.EXE
  • ICSUPP95.EXE
  • ICSUPPNT.EXE
  • IFACE.EXE
  • IFW2000.EXE
  • index.exe
  • IOMON98.EXE
  • IPARMOR.EXE
  • IRIS.EXE
  • ISRV95.EXE
  • JAMMER.EXE
  • JEDI.EXE
  • KAVLITE40ENG.EXE
  • KAVPERS40ENG.EXE
  • KAVPF.EXE
  • KERIO-PF-213-EN-WIN.EXE
  • KERIO-WRL-421-EN-WIN.EXE
  • KERIO-WRP-421-EN-WIN.EXE
  • KILLPROCESSSETUP161.EXE
  • LDNETMON.EXE
  • LDPRO.EXE
  • LDPROMENU.EXE
  • LDSCAN.EXE
  • LOCALNET.EXE
  • LOCKDOWN.EXE
  • lockdown2000.EXE
  • LOCKDOWN2000.EXE
  • lolx.exe
  • LOOKOUT.EXE
  • LSETUP.EXE
  • LUALL.EXE
  • LUAU.EXE
  • LUCOMSERVER.EXE
  • LUINIT.EXE
  • LUSPT.EXE
  • MCAGENT.EXE
  • MCMNHDLR.EXE
  • MCTOOL.EXE
  • MCUPDATE.EXE
  • MCVSRTE.EXE
  • MCVSSHLD.EXE
  • MFW2EN.EXE
  • MFWENG3.02D30.EXE
  • MGAVRTCL.EXE
  • MGAVRTE.EXE
  • mmc.exe
  • msblast.exe
  • mslaugh.exe
  • mspatch.exe
  • Navw32.EXE
  • NeoWatchLog.EXE
  • notstart.EXE
  • NPF40_TW_98_NT_ME_2K.EXE
  • NPFMESSENGER.EXE
  • NPROTECT.EXE
  • npscheck.EXE
  • NPSSVC.EXE
  • NSCHED32.EXE
  • ntrtscan.EXE
  • NTVDM.EXE
  • NTXconfig.EXE
  • Nui.EXE
  • Nupgrade.EXE
  • NVARCH16.EXE
  • NVC95.EXE
  • nvsvc32.EXE
  • NWINST4.EXE
  • NWService.EXE
  • NWTOOL16.EXE
  • OSTRONET.EXE
  • OUTPOST.EXE
  • OUTPOSTINSTALL.EXE
  • OUTPOSTPROINSTALL.EXE
  • PADMIN.EXE
  • PANIXK.EXE
  • PAVCL.EXE
  • pavproxy.EXE
  • PAVPROXY.EXE
  • PAVSCHED.EXE
  • PAVW.EXE
  • PCC2002S902.EXE
  • PCC2K_76_1436.EXE
  • PCCIOMON.EXE
  • pccntmon.EXE
  • pccwin97.EXE
  • PCCWIN98.EXE
  • PCDSETUP.EXE
  • PCFWALLICON.EXE
  • PCIP10117_0.EXE
  • pcscan.EXE
  • PDSETUP.EXE
  • penis32.exe
  • PERISCOPE.EXE
  • PERSFW.EXE
  • PERSWF.EXE
  • PF2.EXE
  • PFWADMIN.EXE
  • PINGSCAN.EXE
  • PLATIN.EXE
  • POP3TRAP.EXE
  • POPROXY.EXE
  • POPSCAN.EXE
  • PORTDETECTIVE.EXE
  • PORTMONITOR.EXE
  • PPINUPDT.EXE
  • PPTBC.EXE
  • PPVSTOP.EXE
  • PROCESSMONITOR.EXE
  • PROCEXPLORERV1.0.EXE
  • PROGRAMAUDITOR.EXE
  • PROPORT.EXE
  • PROTECTX.EXE
  • PSPF.EXE
  • PURGE.EXE
  • PVIEW95.EXE
  • QCONSOLE.EXE
  • QSERVER.EXE
  • rapapp.EXE
  • RAV7.EXE
  • RAV7WIN.EXE
  • RAV8WIN32ENG.EXE
  • REALMON.EXE
  • REGEDIT.EXE
  • REGEDT32.EXE
  • RESCUE.EXE
  • RESCUE32.EXE
  • root32.exe
  • rpc.exe
  • rpctest.exe
  • RRGUARD.EXE
  • RSHELL.EXE
  • rtvscan.EXE
  • RTVSCN95.EXE
  • RULAUNCH.EXE
  • SAFEWEB.EXE
  • sbserv.EXE
  • SBSERV.EXE
  • SCAN32.EXE
  • SCAN95.EXE
  • SCANPM.EXE
  • SCRSCAN.EXE
  • scvhost.exe
  • SD.EXE
  • SERV95.EXE
  • SETUP_FLOWPROTECTOR_US.EXE
  • SETUPVAMEEVAL.EXE
  • SFC.EXE
  • SGSSFW32.EXE
  • SH.EXE
  • SHELLSPYINSTALL.EXE
  • SHN.EXE
  • SMC.EXE
  • SOFI.EXE
  • SPF.EXE
  • Sphinx.EXE
  • SPHINX.EXE
  • SPYXX.EXE
  • SS3EDIT.EXE
  • ST2.EXE
  • SUPFTRL.EXE
  • SUPPORTER5.EXE
  • SWEEP95.EXE
  • SweepNet.SWEEPSRV.SYS.SWNETSUP.EXE
  • SymProxySvc.EXE
  • SYMPROXYSVC.EXE
  • SYMTRAY.EXE
  • SYSEDIT.EXE
  • TASKMON.EXE
  • TAUMON.EXE
  • TBSCAN.EXE
  • TC.EXE
  • TCA.EXE
  • TCM.EXE
  • TDS2-98.EXE
  • TDS2-NT.EXE
  • TDS-3.EXE
  • teekids.exe
  • TFAK.EXE
  • TFAK5.EXE
  • tftpd.exe
  • TGBOB.EXE
  • TITANIN.EXE
  • TITANINXP.EXE
  • TRACERT.EXE
  • TRJSCAN.EXE
  • TRJSETUP.EXE
  • TROJANTRAP3.EXE
  • UNDOBOOT.EXE
  • UPDATE.EXE
  • vbcmserv.EXE
  • VBCMSERV.EXE
  • VbCons.EXE
  • VBCONS.EXE
  • VBUST.EXE
  • VBWIN9X.EXE
  • VBWINNTW.EXE
  • VCSETUP.EXE
  • VET32.EXE
  • Vet95.EXE
  • VET95.EXE
  • VetTray.EXE
  • VETTRAY.EXE
  • VFSETUP.EXE
  • VIR-HELP.EXE
  • VIRUSMDPERSONALFIREWALL.EXE
  • VNLAN300.EXE
  • VNPC3000.EXE
  • VPC32.EXE
  • VPC42.EXE
  • VPFW30S.EXE
  • VPTRAY.EXE
  • VSCAN40.EXE
  • VSCENU6.02D30.EXE
  • VSCHED.EXE
  • VSECOMR.EXE
  • vshwin32.EXE
  • VSISETUP.EXE
  • VSMAIN.EXE
  • vsmon.EXE
  • VSMON.EXE
  • VSSTAT.EXE
  • VSWIN9XE.EXE
  • VSWINNTSE.EXE
  • VSWINPERSE.EXE
  • W32DSM89.EXE
  • W9X.EXE
  • WATCHDOG.EXE
  • WEBSCANX.EXE
  • WEBTRAP.EXE
  • WFINDV32.EXE
  • WGFE95.EXE
  • WHOSWATCHINGME.EXE
  • WIMMUN32.EXE
  • winppr32.exe
  • WINRECON.EXE
  • WNT.EXE
  • worm.exe
  • WrAdmin.EXE
  • WRADMIN.EXE
  • WrCtrl.EXE
  • WRCTRL.EXE
  • WSBGATE.EXE
  • WYVERNWORKSFIREWALL.EXE
  • XPF202EN.EXE
  • zapro.EXE
  • ZAPRO.EXE
  • ZAPSETUP3001.EXE
  • ZATUTOR.EXE
  • ZAUINST.EXE
  • ZONALM2601.EXE
  • zonealarm.EXE
  • ZONEALARM.EXE


Antivirus Protection Dates

  • Initial Rapid Release version February 26, 2004
  • Latest Rapid Release version September 28, 2010 revision 054
  • Initial Daily Certified version February 26, 2004
  • Latest Daily Certified version September 28, 2010 revision 036
  • Initial Weekly Certified release date February 27, 2004

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

Writeup By: John Canavan

Discovered: February 25, 2004
Updated: February 13, 2007 12:18:57 PM
Type: Worm
Systems Affected: Windows


When W32.Mockbot.A.Worm is executed, it performs the following actions:

  1. Attempts to copy itself as the files:
    • %System%\msnet.exe
    • %StartMenu%\Programs\Startup\msnet.exe


      Notes:
    • %System% is a variable. The worm locates the System folder and copies itself to that location. By default, this is C:\Windows\System (Windows 95/98/Me), C:\Winnt\System32 (Windows NT/2000), or C:\Windows\System32 (Windows XP).
    • %StartMenu% is a variable. The worm locates the Start Menu folder and copies itself to that location. By default, this is C:\Windows\Start Menu (Windows 95/98/Me) or C:\Documents and Settings\<current user>\Start Menu (Windows Windows NT/2000/XP).

  2. Spawns a thread that attempts to create the following registry key values below, and then monitors them. The thread will recreate the values if they are deleted.

  3. Adds the value:

    "Microsoft Network" = "%System%\msnet.exe"

    to one or more of the following registry keys:
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      Run
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      RunOnce
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      RunServices
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      RunServicesOnce
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      Run
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      RunOnce
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      RunServices
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      RunServicesOnce

      so that the worm is executed on startup.

  4. Adds the values:
    • "Enable"="Yes"
    • "Path"="%System%\msnet.exe"
    • "Parametres"=""
    • "Startup"="%System%\msnet.exe"

      to the registry key:

      HKEY_CURRENT_USER\Software\Mirabilis\ICQ\Agent\Apps\icqstub

      so that the worm is executed any time ICQ is started.

  5. Attempts to create the service, "Microsoft Network," so that the worm is executed with system-level access privileges on startup.

  6. Spawns a thread that monitors running processes, killing any found on a large list of antivirus, firewall, and security product process names, as well as some viruses and malware. For more details, see the list in the "Additional Information" section below.

  7. The worm will randomly generate IP addresses and use each of the following methods to try to infect computers at each IP:
    • Checks whether the computer is infected with W32.Mydoom.A@mm or Backdoor.Optix. The worm does this by attempting to connect to the computer on ports 3127 and 3410. If these backdoors are found, the worm will install itself on the host.
    • Attempts to connect to the computer on port 6129, looking for the DameWare Mini Remote Control server application. If found, the worm will take advantage of a vulnerability in the application to install itself on the computer.
    • Sends data on TCP port 135 that may exploit the DCOM RPC vulnerability (described in Microsoft Security Bulletin MS03-026). The worm sends one of two types of data, which exploits either Windows XP or Windows 2000. If the exploit is successful, the worm will install itself on the remote host.

  8. Opens a backdoor listening for connections on port 69.

  9. Connects to predetermined IRC servers and joins a channel to listen for commands from an attacker. The worm will report its status and information on any other infected computers.


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: John Canavan

Discovered: February 25, 2004
Updated: February 13, 2007 12:18:57 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. Update the virus definitions.
  3. Do one of the following:
    • Windows 95/98/Me: Restart the computer in Safe mode.
    • Windows NT/2000/XP: End the malicious process.
  4. Run a full system scan and delete all the files detected as W32.Mockbot.A.Worm.
  5. Reverse the changes made to the registry.
For 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:
Note: When you are completely finished with the removal procedure and are satisfied that the threat has been removed, re-enable System Restore by following the instructions in the aforementioned documents.

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. Updating the virus definitions
Symantec Security Response fully tests all the virus definitions for quality assurance before they are posted to our servers. There are two ways to obtain the most recent virus definitions:

  • Running LiveUpdate, which is the easiest way to obtain virus definitions: These virus definitions are posted to the LiveUpdate servers once each week (usually on Wednesdays), unless there is a major virus outbreak. To determine whether definitions for this threat are available by LiveUpdate, refer to the Virus Definitions (LiveUpdate).
  • Downloading the definitions using the Intelligent Updater: The Intelligent Updater virus definitions are posted on U.S. business days (Monday through Friday). You should download the definitions from the Symantec Security Response Web site and manually install them. To determine whether definitions for this threat are available by the Intelligent Updater, refer to the Virus Definitions (Intelligent Updater).

    The Intelligent Updater virus definitions are available: Read "How to update virus definition files using the Intelligent Updater" for detailed instructions.

3. Restarting the computer in Safe mode or ending the malicious process
    Windows 95/98/Me
    Shut down the computer and turn off the power. Wait for at least 30 seconds, and then restart the computer in Safe mode. For instructions, read the document, "How to start the computer in Safe Mode."

    Windows NT/2000/XP
    To end the malicious process:
    1. Press Ctrl+Alt+Delete once.
    2. Click Task Manager.
    3. Click the Processes tab.
    4. Double-click the Image Name column header to alphabetically sort the processes.
    5. Scroll through the list and look for msnet.exe.
    6. If you find the file, click it, and then click End Process.
    7. Exit the Task Manager.
4. 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.Mockbot.A.Worm, click Delete.

5. Reversing the changes made to the registry


WARNING: 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 each of the keys:
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      Run
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      RunOnce
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      RunServices
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
      RunServicesOnce
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      Run
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      RunOnce
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      RunServices
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
      RunServicesOnce

  4. In the right pane, delete the value:

    "Microsoft Network"="%System%\msnet.exe"

  5. Navigate to the key:

    HKEY_CURRENT_USER\Software\Mirabilis\ICQ\Agent\Apps

  6. In the right pane, delete the value:

    "icqStub"

  7. Exit the Registry Editor.

  8. Restart the computer in Normal mode. For instructions, read the section on returning to Normal mode in the document, "How to start the computer in Safe Mode."


Writeup By: John Canavan