Backdoor.IRC.Aladinz.F

Printer Friendly Page

Discovered: January 01, 2004
Updated: February 13, 2007 12:15:39 PM
Also Known As: Win32.Randon.AC [Kaspersky]
Type: Trojan Horse
Systems Affected: Windows


Backdoor.IRC.Aladinz.F is a Backdoor Trojan that uses mIRC client software with malicious mIRC scripts, allowing unauthorized remote access, including launching denial of service attacks and attempting to compromise additional computers.

Antivirus Protection Dates

  • Initial Rapid Release version January 02, 2004
  • Latest Rapid Release version March 23, 2017 revision 037
  • Initial Daily Certified version January 02, 2004
  • Latest Daily Certified version March 23, 2017 revision 041
  • Initial Weekly Certified release date January 07, 2004

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

Writeup By: Eric Chien

Discovered: January 01, 2004
Updated: February 13, 2007 12:15:39 PM
Also Known As: Win32.Randon.AC [Kaspersky]
Type: Trojan Horse
Systems Affected: Windows


Backdoor.IRC.Aladinz.F consists of a self-extracting installer that installs multiple files. When the installer is run, it performs the following actions:

  1. Creates a folder which contains the Trojan files. For example, the installer of Backdoor.IRC.Aladinz.F may create the following folders:
    • %System%\CONFIG\mouse\web\printers\images\system\winnt
    • C:\Documents And and Settings\All Users\Application Data\Microsoft\Network\Connections\tcp
    • %System%\Protect\system\s132\config\bios\data\word\micro
    • %System%\CATROOT\user\admin\system\config\bootup\menu\winderz\microsh*t\sucks\ass\hahaha\
      this\is\funny\sh*t\gay\microsoft


      Note: %System% is a variable. The Trojan 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).

  2. Drops the following files into the folder:
    • Screen.dll: A mIRC script detected as IRC Trojan.
    • Java.dll: A non-malicious mIRC script that installs an IRC Proxy server.
    • Ipservers.dll: A non-malicious configuration file.
    • Restart.exe: A non-malicious tool used to restart the computer.
    • Flood.ocx: A mIRC script detected as IRC Trojan.
    • Sipg.ocx: A mIRC script detected as IRC Trojan.
    • Wind.dll: A mIRC script detected as Backdoor.IRC.Aladinz.F.
    • Uuid.dll: A non-malicious .dll.
    • Newuser.bat: A non-malicious file, which malicious software may use to delete shares on the localhost.
    • Wincmd34.bat: A batch file that connects to remote shares and is detected as BAT.Trojan.
    • Boot.exe: A non-malicious tool used to launch processes across a network. Known as PSExec produced by Sysinternals.
    • Lan.bat: A tool that performs a dictionary attack to connect to ipc$ and ADMIN$ network shares. It attempts to connect and run Msmouse.exe using the Psexec tool. This file is detected as BAT.Trojan.
    • Msmouse.exe: A tool that downloads the installer for Backdoor.IRC.Aladinz.F from a hard-coded URL.
    • Regedit.dll: A non-malicious mIRC script that modifies the registry.
    • Sysconfig.ocx: A mIRC script detected as IRC Trojan.
    • Mscfg32bit.exe: A legitimate proxy from www.youngzsoft.com, named CCProxy. It may be used to anonymously send spam through an infected computer.
    • Msninfo.ini: A non-malicious configuration file for CCProxy.
    • Lsass.exe: A mIRC client.
    • Sysboot.dll: A non-malicious mIRC script.
    • Moo.dll: A non-malicious .dll used to collect system information.
    • Nhtml.dll: A non-malicious .dll capable of sending messages to the mIRC client window.
    • Tvchost32.exe: A command-line tool that accepts the target's IP and port to perform a DoS attack. This file is detected as Hacktool.Flooder.
    • Libparse.exe: A non-malicious process management utility named PrcView.
    • Empavms.exe: A non-malicious HideWindow tool used to hide other applications (for example, to hide the mIRC client).
    • AccInfo.ini: A non-malicious configuration file.
    • Remote.ini: A mIRC configuration file that is used for malicious purposes. This file is detected as Backdoor.IRC.Aladinz.F.
    • Conn.txt: Renamed Moo.dll, which is a non-malicious DLL used to collect system information.
    • Cygwin1.dll: A non-malicious DLL.
    • Network.dll: A clean dictionary text file.
    • NITE.exe: A command-line tool that performs DoS attacks. This file is detected as Hacktool.Flooder.
    • Os32.dll: A mIRC configuration script that is detected as Backdoor.IRC.Aladinz.F.
    • Pnp11.exe: A non-malicious HideWindow tool used to hide other applications (for example, to hide the mIRC client).
    • SMSS.exe: A mIRC client.
    • VLXD.bat: A batch file that connects to remote shares. This file is detected as Backdoor.IRC.Aladinz.F.
    • VLXD.cfg: A clean text file.
    • VLXD.exe: A program that downloads additional components from the Internet.
    • Winconfig.exe: A non-malicious process control tool.
    • Winos.dll: A mIRC configuration script.
    • Winx.dll: A mIRC configuration script.
    • H.exe: A non-malicious program that executes a program while hiding its window.
    • Psc32.exe: A non-malicious tool used to launch processes across a network. Known as PSExec produced by Sysinternals.
  3. Adds the values:

    "lsass" = "<path to lsass.exe>"
    "smss" = "<path to smss.exe>"

    to the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

    so that the Trojan starts when you start or restart Windows.
  4. By default, the Trojan allows the hacker to perform any of the following actions:
    • Download and execute files.
    • Perform DoS attacks against predetermined targets.
    • Use the installed proxy server for malicious purposes.
    • Attempt to compromise further machines via open shares or weak passwords.


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: Eric Chien

Discovered: January 01, 2004
Updated: February 13, 2007 12:15:39 PM
Also Known As: Win32.Randon.AC [Kaspersky]
Type: Trojan Horse
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. Do one of the following:
    • Windows 95/98/Me: Restart the computer in Safe mode.
    • Windows NT/2000/XP: End the malicious process.
  4. Run a full system scan and delete all detected files.
  5. Reverse the changes made to the registry.
For details on each of these steps, read the following instructions.

1. Disabling 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:
Note: When you are completely finished with the removal procedure, and you are satisfied that the threat has been removed, you should reenable 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. Updating 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. Restarting the computer in Safe mode or ending the malicious process
    Windows 95/98/Me
    Shut down the computer and turn off the power. Wait for at least 30 seconds, and then restart the computer in Safe mode. For instructions on how to do this, read the document, "How to start the computer in Safe Mode."

    Windows NT/2000/XP
    To end the malicious process:
    1. Press Ctrl+Alt+Delete once.
    2. Click Task Manager.
    3. Click the Processes tab.
    4. Double-click the Image Name column header to alphabetically sort the processes.
    5. Scroll through the list and look for LSASS and SMSS.
    6. If you find one or both of the processes running, click the process to highlight it, and then click End Process.
    7. Exit the Task Manager.
4. Scanning for and deleting 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, click Delete.

5. Reversing the changes made to the registry


WARNING: 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. (The Run dialog box appears.)
  2. Type regedit

    Then click OK. (The Registry Editor opens.)

  3. Navigate to the key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

  4. In the right pane, delete the values:

    "lsass"
    "smss"
  5. Exit the Registry Editor.


Writeup By: Eric Chien