Printer Friendly Page

Discovered: July 03, 2004
Updated: February 13, 2007 12:25:00 PM
Also Known As: Win32.Evaman [Computer Associa, WORM_EVAMAN.A [Trend], W32/Evaman@MM [McAfee], W32/Evaman-A [Sophos], I-Worm.Evaman.a [Kaspersky]
Type: Worm
Systems Affected: Windows

W32.Evaman@mm is a mass-mailing worm that spreads to addresses found at the Web site, email.people.yahoo.com.

The worm arrives as an attachment with an .exe or .scr extension.

Note: Symantec Consumer products that support Worm Blocking functionality automatically detect this threat as it attempts to spread.

Antivirus Protection Dates

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

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

Writeup By: Heather Shannon

Discovered: July 03, 2004
Updated: February 13, 2007 12:25:00 PM
Also Known As: Win32.Evaman [Computer Associa, WORM_EVAMAN.A [Trend], W32/Evaman@MM [McAfee], W32/Evaman-A [Sophos], I-Worm.Evaman.a [Kaspersky]
Type: Worm
Systems Affected: Windows

When W32.Evaman@mm is executed, it does the following:

  1. May launch Notepad.exe the first time it is executed.

  2. Creates the registry key:


  3. Copies itself as %System%\wintasks.exe.

    Note: %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).

  4. Adds the value:


    to the registry key:


    so that the worm runs when you start Windows.

  5. Selects an SMTP server from the following hard-coded list:
    • smtp.rcn.com
    • outgoing.verizon.net
    • smtp.comcast.net
    • mail.mindspring.com
    • smtp.email.msn.com
    • smtpauth.earthlink.net
    • smtp-server.nc.rr.com
    • smtp1.attglobal.net
    • mailhost.att.net
    • mail.optonline.net
    • mail.peoplepc.com
    • smtpout.bellatlantic.net
    • mail.verio.net
    • smtp.netzero.net
    • smtp.prodigy.net

  6. The worm uses the first SMTP server that it successfully connects to. If it is unable to connect to any of these servers, the worm queries the registry key:

    HKEY_CURRENT_USER\Software\Microsoft\Internet Account Manager\Accounts\SMTP Server

    to find a mail server.

  7. Generates random queries to email.people.yahoo.com, and collects email addresses from the search results.

  8. Sends itself to the addresses that it finds.

    The message has the following characteristics:

    From: (spoofed)

    Subject: (One of the following)
    • Delivery Status (Failure)
    • failed transaction
    • failure delivery
    • mail failure
    • returned mail
    • server error

      Message: (One of the following)
    • This is an automatically generated Delivery Status Notification.
      Delivery to last recipient failed.
      Email returned as attachment text file.
    • Message from Mail Delivery Server.
      Unable to deliver message to last recipient.
      Email returned as text file.
    • Email returned by the server as ASCII Text mail file.
      To read the email download the included attachment.
    • Mail Server Notice:
      Last email sent could not reach intented destination.
      Email returned as ASCII text file.
    • The last email sent by this account could not reach intended destination.
      Email has been returned as text file attachment.
    • Mail Delivery Status Notification:
      Message returned by server. Message returned as text file attachment.

      The attachment has the form:

      <first part>.<last part>

      where <first part> is one of the following:
    • body
    • message
    • email
    • returned
    • text
    • document

      and <last part> is one of the following:
    • scr
    • txt.scr
    • html.scr
    • outlook.scrtxt.exe


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: Heather Shannon

Discovered: July 03, 2004
Updated: February 13, 2007 12:25:00 PM
Also Known As: Win32.Evaman [Computer Associa, WORM_EVAMAN.A [Trend], W32/Evaman@MM [McAfee], W32/Evaman-A [Sophos], I-Worm.Evaman.a [Kaspersky]
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. Restart the computer in Safe mode or VGA mode.
  4. Run a full system scan and delete all the files detected as W32.Evaman@mm.
  5. Delete the value that was added to the registry.
For specific details on each of these steps, read the following instructions.

1. To disable 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:

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. To update 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. To restart the computer in Safe mode or VGA mode

Shut down the computer and turn off the power. Wait for at least 30 seconds, and then restart the computer in Safe mode or VGA mode.
  • For Windows 95, 98, Me, 2000, or XP users, restart the computer in Safe mode. For instructions, read the document, "How to start the computer in Safe Mode."
  • For Windows NT 4 users, restart the computer in VGA mode.

4. To scan for and delete 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.Evaman@mm, click Delete.

    If your Symantec antivirus product reports that it cannot delete an infected file, Windows may be using the file. To fix this, run the scan in Safe mode. For instructions, read the document, "How to start the computer in Safe Mode." Once you have restarted in Safe mode, run the scan again.

    (After the files are deleted, you can leave the computer in Safe mode and proceed with section 4. When that is done, restart the computer in Normal mode.)

5. To delete the value from the registry

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 > Run.
  2. Type regedit

    Then click OK.

  3. Navigate to the key:


  4. In the right pane, delete the value:


  5. Navigate to and delete the key

  6. Exit the Registry Editor.

Writeup By: Heather Shannon