W97M.Service.A

W97M.Service.A infects the Microsoft Word 97 global template upon opening an infected file. Once the global template is infected, the virus infects other documents upon closing it. It infects by replacing the default class module, ThisDocument, with a viral one, NOSN.

W97M.Service.A is polymorphic. It also contains many encrypted strings. One of its payloads is to email itself using Outlook. This macro virus is similar to Melissa.

The mass email routine
The virus checks to see if it has completed the mass emailing before by reviewing the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Office\ for a value of "NOSN".

The value data is set to "Non au Service National - Oui au Contrat de Travail" if the mass emailing has been completed on the current machine. If it does not find the registry entry, it will do the mass emailing.

The email is composed randomly. There are three possible email messages:

1. Subject line is:
   Suggestion...
   
   and the email body is:
   Ce document (NOARMY-A.doC) vaut bien un petit coup d'oeil. J'aimerais savoir s'il correspond à ce qu'on attends de lui.
   
2. Subject line is:
   Un peu d'aide...
   
   and the email body is:
   Je dois avouer que j'ai un peu de mal à peaufiner ce document (NOARMY-A.doC). Merci de m'aider un peu pour l'améliorer...
   
3. Subject line is:
   Version finale
   
   and the email body is:
   Voici la dernière version de ce sur quoi j'ai travaillé ces derniers temps (NOARMY-A.doC).Tous les avis sont la bienvenue !

The worm attaches the (infected) active document to the email message.

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.

Summary