Printer Friendly Page

Discovered: February 01, 2002
Updated: February 13, 2007 11:49:02 AM
Also Known As: W32.Secup
Type: Worm

W32.Redesi.C@mm is a mass-mailing worm written in Visual Basic. This worm sends itself to all the contacts in the Microsoft Outlook Address Book.

W32.Redesi.C@mm is a variant of W32.Redesi.B@mm . This variant arrives as a forwarded message, and in many cases, an individual you may know sends the message. The forwarded message has been crafted so that it appears to be an authentic security update from Microsoft.

This variant has a few FW (forwarded subject lines) it can choose from.

Such forwarded messages are not from Microsoft. Microsoft does not send patches or updates by email.

Antivirus Protection Dates

  • Initial Rapid Release version February 04, 2002
  • Latest Rapid Release version September 28, 2010 revision 054
  • Initial Daily Certified version February 04, 2002
  • Latest Daily Certified version September 28, 2010 revision 036
  • Initial Weekly Certified release date February 06, 2002

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

Writeup By: Gor Nazaryan

Discovered: February 01, 2002
Updated: February 13, 2007 11:49:02 AM
Also Known As: W32.Secup
Type: Worm

When this worm is executed, it:

  1. Copies of itself as:
    • C:\Loadme.exe
    • C:\News.exe
    • C:\Si.exe
    • C:\SetupMSI.exe
    • C:\load.exe

  2. Displays the following message:

    Your Windows Update has been successful.
  3. Adds a reference to one of the aforementioned files to the following registry key:

  4. Sends itself to all the recipients in the Microsoft Outlook address book. The email message has the following characteristics:
    Subject: The Subject is one of the following:
    • FW: Security Update by Microsoft.
    • FW: Microsoft security update.
    • FW: IT departments on state of HIGH ALERT.
    • FW: Important news from Microsoft.
    • FW: Stop terrorists computer viruses reign.
    • FW: Terrorists release computer virus.
    • FW: Emergency response from Microsoft Corp.
    • FW: Terrorist Emergency. Latest virus can wipe disk in minutes.
    • FW: Microsoft Update. Final Release Candidate.
    • FW: New computer virus.

    Just recieved this in my email
    I have contacted Microsoft and they say it's real !

    -----Original Message-----
    From: Microsoft Support Desk [mailto:Support@microsoft.com]
    Sent: 17 October 2001 15:21
    Subject: Security Update
    Due to the recent spate of email spread computer viruses Microsoft Corp has released a security patch.
    Please apply the attached file to your Windows computer to stop any futher spread or these malicious programs.
    Microsoft Support

    Attachment: The Attachment is one of the following files:
    • C:\Loadme.exe
    • C:\News.exe
    • C:\Si.exe
    • C:\SetupMSI.exe
    • C:\load.exe
5. Also appended two instructions to the C:\Autoexec.bat startup file, if the worm ran on November 11, 2001.
    • The first instruction is an "echo" statement that displayed a message referring to "Wicca."
    • The second line is an instruction to format the C drive.

NOTE: This does not affect Windows NT/2000/XP computers.


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: Gor Nazaryan

Discovered: February 01, 2002
Updated: February 13, 2007 11:49:02 AM
Also Known As: W32.Secup
Type: Worm

To remove this worm, delete all the files detected as W32.Redesi.C@mm and remove the value that the worm added to the registry. Edit the Autoexec.bat, if necessary.

Removing the worm

  1. Run LiveUpdate to make sure that you have the most recent virus definitions.
  2. Start Norton AntiVirus (NAV) and make sure that NAV is configured to scan all the files. For instructions on how to do this, read the document, "How to configure Norton AntiVirus to scan all files."
  3. Run a full system scan.
  4. Delete all the files detected as W32.Redesi.C@mm.

Editing the registry

CAUTION : We strongly recommend that you back up the registry before you make 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 back up the Windows registry ," for instructions.
  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 key:

  4. In the right pane, look for a reference to one of the following files:
    • C:\Loadme.exe
    • C:\News.exe
    • C:\Si.exe
    • C:\SetupMSI.exe
    • C:\load.exe
  5. Delete this value.
  6. Click Registry, and then click Exit.

Editing the Autoexec.bat file
If the worm ran on November 11, 2001 and you are using Windows 95/98/Me, to prevent the data loss on the C drive, follow these steps before restarting the computer:
  1. Click Start, and then click Run.
  2. Type the following:

    edit c:\autoexec.bat

    and then click OK.

    (The MS-DOS Editor opens.)
  3. Delete the following lines that begin with this text:

    ECHO Bide ye the ...
    format C: /autotest
  4. Click File, and then click Save.
  5. Click File, and then click Exit.

Writeup By: Gor Nazaryan