Backdoor.Nibu.D

Printer Friendly Page

Discovered: April 06, 2004
Updated: February 13, 2007 12:21:04 PM
Also Known As: Bloodhound.Exploit.6, W32/Dumaru.w.gen [McAfee], Exploit-MhtRedir [McAfee]
Type: Trojan Horse
Systems Affected: Windows


Backdoor.Nibu.D is a Trojan horse that attempts to steal passwords and bank account information.



Backdooor.Nibu.D could have originally been emailed containing the text below. This email attempts to exploit a vulnerability in Internet Explorer that allows for arbitrary code execution.

Definitions released prior to April 6, 2004 detect these email messages as Bloodhound.Exploit.6.


Subject: Receipt of Payment

Dear friend,
 
Thank you for your purchase!
This message is to inform you that your order has been received
and will be processed shortly.  
 
Your account is being processed for $79.85, for a 3 month term.  
You will receive an account setup confirmation within the next
24 hours with instructions on how to access your account.  
If you have any questions regarding this invoice,
please feel free to contact us at <link blocked>.
We appreciate your business and look forward to a great relationship!
 
Thank You,
 
The Hashshanklin Team
 
 
ORDER SUMMARY
-------------
 
 
Web Hosting............. $29.85
Setup................... $30.00
 
Domain Registration..... $20.00
Sales Date.............. 04/04/2004
Domain.................. sexigerl.com
 
Total Price............. $79.85
Card Type............... Visa


Another variation of this email refers to "The Tekriter.com Team." It does not use the Bloodhound.Exploit.6 exploit, but clicking the link in the email causes the Trojan to be installed as follows:

  • The link points to a Web site with an embedded object tag, containing a link to 2.php.
  • 2.php is a .html file containing VBScript commands to drop and execute the file, rtq.vbs.
  • Rtq.vbs uses the ADODB stream objects vulnerability to download and execute a file titled ukam.gif. (This file is an executable, not a .gif image.) It is saved as svchostss.exe.
  • Svchostss.exe downloads and installs Backdoor.Nibu.D.


Antivirus Protection Dates

  • Initial Rapid Release version April 06, 2004
  • Latest Rapid Release version March 23, 2017 revision 037
  • Initial Daily Certified version April 06, 2004
  • Latest Daily Certified version March 23, 2017 revision 041
  • Initial Weekly Certified release date April 06, 2004

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


Technical Description


When Backdoor.Nibu.D is executed, it does the following:

  1. Copies itself as these files:
    • %System%\Load32.exe
    • %Startup%\Rundllw.exe
    • %Windir%\Dllreg.exe
    • %System%\Vxdmgr32.exe


      Notes:
      • %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).
      • %Startup% is a variable. The worm locates the Windows startup folder and copies itself to that location. For example, this is C:\Windows\Start Menu\Programs\Startup (Windows 95/98/Me) or C:\Documents and Settings\<current user>\Start Menu\Programs\Startup (Windows NT/2000/XP).
      • %Windir% is a variable. The worm locates the Windows installation folder (by default, this is C:\Windows or C:\Winnt) and copies itself to that location.


  2. Adds the value:

    "load32"="%System%\load32.exe"

    to the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

    so that the Trojan runs when you start Windows.

  3. Creates and loads a .dll file to capture keystrokes. Known variants have used the following file names:
    • %Windir%\sock32.dll
    • %Windir%\sock55.dll
    • %Windir%\sock64.dll

  4. May create the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\SARS

  5. Modifies the [windows] section of the Win.ini file (Windows 95/98/Me only) to:

    [windows]
    run=%Windir%\dllreg.exe

  6. Modifies the [boot] section of the System.ini file (Windows 95/98/Me only) to:

    [boot]
    shell=explorer.exe %System%\vxdmgr32.exe

    so that the worm runs when you start Windows 95/98/Me.

  7. Modifies the value data of:

    Shell

    in the registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

    from:

    "explorer.exe"

    to:

    "explorer.exe %Windir%\system32\vxdmgr32.exe"

    so that the worm runs when you start Windows NT/2000/XP.

  8. Looks for windows that have certain strings in the title bar. These strings vary, but may include the following:
    • @NetMan
    • westpac
    • money
    • pay
    • hsbc
    • bank
    • halifax
    • barclays
    • punk
    • banco
    • e-gold Account
    • Hong Leong
    • Yahoo! mail
    • SignOn
    • SignIn
    • credit report logon
    • Login
    • LogOn


      Note: Typically, such windows would be Web browser windows displaying logon screens for financial services or email accounts.

  9. Captures keystrokes that are typed into windows with the above strings and stores them in a log file. This file may be named %Windir%\vxdload.txt or %Windir%\bank.log.

  10. Launches a thread that monitors the Clipboard, saving any data that is found to a log file. This file may be named %Windir%\rundllx.sys.

  11. If the logon page for Barclays bank is visited, the Trojan will attempt to create screenshots of specific parts of that page. The screenshots will be saved as %windir%\bank1.bmp and windir%\bank2.bmp.

  12. Periodically checks the size of the files it uses for logging stolen information. When the files are a certain size, the log files will be emailed to a hard-coded email address, along with System information such as the IP address and operating system. The Trojan also attaches the previously mentioned screenshots.


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.


Removal


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. Restart the computer in Safe mode (Windows 95/98/Me) or Safe mode with Command Prompt (Windows 2000/XP).
    4. Reverse the changes made to the registry.
    5. Reverse the changes made to the system files (Windows 95/98/Me).
    6. Restart the computer in Safe mode or VGA mode (Windows 2000/XP).
    7. Run a full system scan and delete all the files detected as Backdoor.Nibu.D.
    For details on each of these steps, read the following instructions.

    1. To disable 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 are satisfied that the threat has been removed, re-enable 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. To update 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. To restart the computer in Safe mode or Safe mode with Command Prompt
    Follow the instructions for your operating system.

    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, read the document, "How to start the computer in Safe Mode."

    Once in Safe mode (this could take some time) proceed with section 4.

    Windows 2000
    1. Shut down the computer and turn off the power. Wait for at least 30 seconds, and then restart the computer.
    2. When you see the black and white Starting Windows bar at the bottom of the screen, press the F8 key (This is usually on the top row of the keyboard).
    3. In the Windows 2000 Advanced Options Menu, select Safe mode with Command Prompt, and then press Enter.

      Once the computer opens to a window with a command prompt (you should see a line of text and a blinking cursor), proceed with section 4.

    Windows XP
    1. Shut down the computer and turn off the power. Wait for at least 30 seconds, and then restart the computer. The computer will begin processing a set of instructions known as the Basic Input/Output System (BIOS). What is displayed depends on the BIOS manufacturer. Some computers display a progress bar that refers to the word BIOS, while others may not display any indication that this process is occurring.
    2. As soon as the BIOS has finished loading, begin tapping the F8 key on your keyboard. Continue to do so until the Windows Advanced Options menu appears. If you begin tapping the F8 key too soon, some computers display a "keyboard error" message. To avoid this, restart the computer and try again.
    3. In the Windows 2000 Advanced Options Menu, select Safe mode with Command Prompt and press Enter.

      Once the computer opens to a window with a command prompt (you should see a line of text and a blinking cursor), proceed with section 4.


    4. To reverse 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. Do one of the following:
      • Windows 2000/XP. Skip to step b.
      • Windows 95/98/Me. Click Start, and then click Run.

    2. Type the following:

      regedit

    3. Do one of the following:
      • Windows 2000/XP: Press Enter.
      • Windows 95/98/Me: Click OK.

    4. Navigate to the key:

      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

    5. In the right pane, delete the value:

      "load32"="%System%\swchost.exe"

    6. Do one of the following:
      • Windows 95/98/Me. Skip to step i.
      • Windows NT/2000/XP: Proceed with step g.

    7. Navigate to the key:

      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

    8. In the right pane, double-click:

      Shell

    9. Change:

      "explorer.exe %Windir%\system32\vxdmgr32.exe"

      to:

      "explorer.exe"

    10. Exit the Registry Editor.
    11. Do one of the following:
      • Windows 95/98/Me. Proceed with section 5.
      • Windows NT/2000/XP: Skip to section 7.

    5. To reverse changes made to system files
    If you are running Windows 95/98/Me, follow these steps:
    1. The function you perform depends on your operating system:
      • Windows 95/98: Go to step b.
      • Windows Me: If you are running Windows Me, the Windows Me file-protection process may have made a backup copy of the System.ini and Win.ini files that you need to edit. If these copies exist, they will be in the C:\Windows\Recent folder. Symantec recommends that you delete these files before continuing with the steps in this section. To do this:
        1. Start Windows Explorer.
        2. Browse to and select the C:\Windows\Recent folder.
        3. In the right pane, select the System.ini file and Win.ini files and delete each one. Windows will regenerate the files.

    2. Click Start, and then click Run.

    3. Type the following, and then click OK.

      edit c:\windows\system.ini

      (The MS-DOS Editor opens.)

      Note: If Windows is installed in a different location, make the appropriate path substitution.

    4. In the [boot] section of the file, look for a line similar to:

      shell = Explorer.exe C:\WINDOWS\SYSTEM\vxdmgr32.exe

    5. If this line exists, delete everything to the right of:

      Explorer.exe

      When you are done, it should look like:

      shell = Explorer.exe

    6. Click File, and then click Save.

    7. Click File, and then click Exit.

    8. Click Start, and then click Run.

    9. Type the following, and then click OK:

      edit c:\windows\win.ini

      (The MS-DOS Editor opens.)

      Note: If Windows is installed in a different location, make the appropriate path substitution.

    10. In the [windows] section of the file, look for a line similar to:

      run=%Windir%\dllreg.exe

    11. If you find it, delete the entire line.

    12. Click File, and then click Save.

    13. Click File, and then click Exit.


Writeup By: Scott Gettis