W32.Matcher.Worm

Printer Friendly Page

Discovered: April 18, 2001
Updated: February 13, 2007 11:36:14 AM
Type: Worm


W32.Matcher is an executable that arrives by email. When executed, the worm will email itself to everyone in the Microsoft Outlook Address book. The worm will continue to send emails while the process is running in the background.

Antivirus Protection Dates

  • Initial Rapid Release version April 18, 2001
  • Latest Rapid Release version March 01, 2011 revision 037
  • Initial Daily Certified version April 18, 2001
  • Latest Daily Certified version March 02, 2011 revision 002

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

Writeup By: Eric Chien

Discovered: April 18, 2001
Updated: February 13, 2007 11:36:14 AM
Type: Worm


W32.Matcher is an email worm that arrives as:

Subject:  Matcher

Message: Want to find your love mates!!! Try this its cool... Looks and Attitude Maching to opposite sex.

When executed, the worm does the following:

  1. Copies itself to the \Windows\System folder as Matcher.exe.
  2. Next, the worm adds the following value:

    (Default)    <\Windows\System folder> \Matcher.exe

    to the registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\
    Windows\CurrentVersion\Run

    This will execute the worm when Windows starts.
  3. The worm then sends itself to everyone in the Outlook Address book with the previously mentioned email. The worm will continue to send emails in an infinite loop.
  4. The worm also modifies the C:\Autoexec.bat file, and appends the lines:

    @echo off
    echo from: Bugger
    pause


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: Eric Chien

Discovered: April 18, 2001
Updated: February 13, 2007 11:36:14 AM
Type: Worm


To remove this worm, delete all detected files, remove the entry that it made to the registry \Run key, and delete the entry that it made to the \Autoexec.bat file.

To remove this worm:

  1. Run LiveUpdate to make sure that you have the most recent virus definitions.
  2. Start Norton AntiVirus (NAV), and then run a full system scan, making sure that NAV is set to scan all files.
  3. Delete any files detected as W32.Matcher

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 then click Run. The Run dialog box appears.
  2. Type regedit and then click OK. The Registry Editor opens.
  3. Navigate to the following subkey:

    HKEY_LOCAL_MACHINE\Software\Microsoft\
    Windows\CurrentVersion\Run

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

    (Default)    <\Windows\System folder> \Matcher.exe
  5. Click Registry and then click Exit to save the changes.

To edit the Autoexec.bat file:
  1. Click Start and then click Run.
  2. Type the following and then press Enter:

    edit c:\autoexec.bat
  3. Locate the following lines and delete them:

    @echo off
    echo from: Bugger
    pause
  4. Click File and then click Save.
  5. Click File and then click Exit.


Writeup By: Eric Chien