Backdoor.IRC.Aladinz.D

1. Drops the following components into the %System% folder:
   
   

   ---

   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).
   

   ---

   
   
   • Windows.exe, which is an ASPacked mIRC client. It is 521,728 bytes.
   • Psexec.exe, which is a UPX-packed remote execution utility used to launch processes. It is 35,328 bytes.
   • Exit.exe, which is a UPX-packed utility used to view running processes. It is 25,600 bytes.
   • Secure.exe, which is a UPX-packed utility used to hide windows. It is 19,456 bytes.
     
     

     ---

     Note: The aforementioned files are not viral and legitimate applications can use them. Symantec antivirus products do not detect them as viral.

     ---

     
     
   • Secure.bat, which is a batch file used to delete open shares. It is 1,063 bytes.
   • Spread.bat, which is a batch file used to remotely log on and launch files. It is 10,753 bytes, and Norton AntiVirus detects it as Backdoor.IRC.Aladinz.D.
     Backdoor.IRC.Aladinz.D uses this batch file to connect to remote IPC$ shares on each of the IP addresses it finds, using various username and password pairs.
     
     For example, Spread.bat may try the user name, "Administrator," with these passwords:
     • xxyyzz
     • <blank>
     • admin
     • Administrator
     • test
     • test123
     • temp
     • temp123
     • pass
     • password
     • password123
     • secret
     • changeme
     • 123456
     • 654321
     • abc123
     • red123
     • admin123
     • qwertyuiop
     • 1
     • 123
     • 12345
     • 54321
     • asdf
       
       
   • System.sys, which is an IRC script file used to copy the Trojan downloader (neci.exe) to remote network shares. It is 35,232 bytes, and Norton AntiVirus detects it as Backdoor.IRC.Aladinz.D.
   • Neci.exe, which is a FSG-packed Win32 executable file that downloads the Backdoor.IRC.Aladinz.D installer from some predefined Web sites. It is 1,104 bytes, and Norton AntiVirus detects it as Download.Trojan.
   • D32.sys, which is an mIRC configuration file that the Trojan uses to load other IRC scripts, such as read.sys, root.sys, system.sys, and winnt.sys. It is 2,499 bytes, and Norton AntiVirus detects it as Backdoor.IRC.Aladinz.D.
   • Read.sys, which is an IRC script file. It is 232 bytes.
   • Root.sys, which is an IRC script file that the mIRC client uses to perform DDOS attacks. It is 29,999 bytes, and Norton AntiVirus detects it as IRC Trojan.
   • Zr.bat, which is a batch file used to add/delete/display the user and local groups. It is 168 bytes.
   • Winnt.sys, which is an empty file.
     
     
2. Adds the value:
   
   "windows"="%System%\windows.exe"
   
   to the registry key:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
   
   So that the mIRC client program runs each time you start Windows.
   
   
3. Creates the subkey, mIRC, in the registry key:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\
   
   and adds the following values to this subkey:
   
   "DisplayName"="mIRC"
   "UninstallString"="%System%\windows.exe -uninstall"
   
   
4. Creates the subkey, .cha,.chat, in the registry:
   
   HKEY_CLASSES_ROOT
   
   and adds the following values to this subkey:
   
   "Default"="Chatfile"

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.