W32.Annew.A

Risk Level 2: Low

Printer Friendly Page

Discovered: February 8, 2007
Updated: March 27, 2007 11:31:54 AM
Also Known As: W32/Annew-A [Sophos], Pahooka.A [Panda Software]
Type: Worm
Infection Length: 214,016 bytes
Systems Affected: Windows 98, Windows 95, Windows XP, Windows Me, Windows NT, Windows 2000

When the worm executes it creates the following files:
  • %UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\Quick Launch.exe
  • %CommonProgramFiles%\default.exe
  • %CommonProgramFiles%\Explorer.exe
  • %System%\msnmsgr.exe
  • %System%\MsFirewall.exe
  • %Windir%\msdos.pif
  • %SystemDrive%\[FILENAME].exe
  • %CommonProgramFiles%\micro~s1\autoexec.bat
The file %SystemDrive%\[FILENAME].exe may be copied multiple times under different file names depending on how many times the worm executes. The variable [FILENAME] can be one of the following:
  • Symantec
  • Nod32
  • Mcafee
  • Bitdefender
  • Sophos
  • Avast
  • Panda
  • Kaspersky
  • Avg
  • F-Secure
  • Security
  • norton
  • Trend
  • Deepguard
  • scan
  • Jack
  • Eset
  • anti
  • Music
  • Books
  • Love
  • Star
  • Games
  • EBooks
  • Computer
  • Pizza
  • Home
  • Photos
  • Shop
  • Adobe
  • Internet
  • Program Files
  • Sex
  • NoteBook
  • Sky
  • My Pictures
  • MyPictures
  • Files
  • Downloads
  • Norton
  • Girls
  • Girlsns
  • Cartoons
  • Microsoft
  • Pacman
  • KingKong
  • Teens
  • Windows
  • Thailand
  • Zoo
  • JetCar
The worm then adds the following lines to the file %SystemDrive%\autorun.inf, so that the worm executes whenever a removable storage deviced is attached to another computer:
[AutoRun]
Open=[FILENAME].exe
shellexecute=[FILENAME].exe
shell\Auto\command=[FILENAME].exe
Shell=Auto

Next, the worm creates the following registry entries so that it executes whenever Windows starts:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\"Shell" = "Explorer.exe %windir%\msdos.pif"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\"MsnMsgr" = "%System%\msnmsgr.exe"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\"MsnMsgr" = "C:\WINDOWS\system32\msnmsgr.exe"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\"Microsoft Personal Firewall" = "%System%\MsFirewall.exe"
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\"Microsoft Personal Firewall" = "%System%\MsFirewall.exe"

The worm then modifies the following registry entries in order to disable some system software:
HKEY_CLASSES_ROOT\exefile\shell\open\command\"(default)" = "%CommonProgramFiles%\Explorer.exe "%1" %*"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\System\"DisableRegistryTools" = "1"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\System\"DisableCMD" = "1"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\System\"DisableTaskMgr" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System\"DisableRegistryTools" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System\"DisableCMD" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System\"DisableTaskMgr" = "1"

It modifies the following registry entries to disable System Restore:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\SystemRestore\"DisableConfig" = "1"
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\SystemRestore\"DisableSR" = "1"

The worm also modifies the following registry entries:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\"NoFolderOptions" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\"Norun" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\"NoFind" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\"NoSetFolders" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\"NoLogoff" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\"Hidden" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\"Hidden" = "0"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\"HideFileExt" = "0"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\"HideFileExt" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\"ShowSuperHidden" = "1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\"ShowSuperHidden" = "0"

The worm then displays the following error message:

Title:
Application Error
Message:
0xFFFFFFFF

The worm changes the title of all visible windows to the following:
[^_^Anti Antivirus^_^]

The worm then ends any processes that contain any of the following strings:
  • cmd
  • mconfig
  • task
  • Proc
  • Hex
  • spy
  • mon
  • AntiVir
  • Reg
  • sca
  • wall
  • ja
  • vp
  • ca
  • av
It also attempts do delete all files in the following folders when %CommonProgramFiles%\micro~s1\autoexec.bat is executed:
  • c:\progra~1\eset\
  • c:\progra~1\kasper~1\
  • c:\progra~1\Symantec\
  • c:\progra~1\Bitdef~1\
  • d:\progra~1\eset\
  • d:\progra~1\kasper~1\
  • d:\progra~1\Symantec\
  • d:\progra~1\Bitdef~1\
The worm may attempt to download and execute the following files:
  • [http://]www.pakahoo.0catch.com/III[REMOVED]
  • [http://]www.pakahoo.0catch.com/FFF[REMOVED]
  • [http://]www.pakahoo.0catch.com/NNN[REMOVED]

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: Stephen Doherty
Search by name
Example: W32.Beagle.AG@mm
Symantec DeepSight Screensaver