Symantec United States
global sites
products
purchase
support
security response
downloads
about symantec
search
feedback



© 1995-2002 Symantec Corporation.
All rights reserved.
Legal Notices
Privacy Policy

security response

W32.Lamin

Category1
Discovered on: December 09, 2002
Last Updated on: December 09, 2002 03:11:30 PM

W32.Lamin is a virus that infects Portable Executable (PE)* files. The virus also contains a keystroke logger and an IRC backdoor Trojan.

NOTE: Definitions that have dates earlier than December 9, 2002, may detect this threat as BloodHound.W32.1.


Type: Virus
Infection Length: 1212 bytes
Systems Affected: Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows Me
Systems Not Affected: Windows 3.x, Microsoft IIS, Macintosh, OS/2, Unix, Linux

protection

  • Virus Definitions (Intelligent Updater) *
  • December 10, 2002

  • Virus Definitions (LiveUpdate™) **
  • December 11, 2002

    *

    Intelligent Updater virus definitions are released daily, but require manual download and installation.
    Click here to download manually.

    **

    LiveUpdate virus definitions are usually released every Wednesday.
    Click here for instructions on using LiveUpdate.

    threat assessment

    Wild:

    Threat Metrics

    Low Low Low

    Wild:
    Low

    Damage:
    Low

    Distribution:
    Low


    technical details

    When a file that is infected with W32.Lamin runs, the virus attempts to do the following:

    Decryption
    W32.Lamin is a polymorphic virus. This means that the virus is encrypted, and that the encryption changes between infections. Because the viral body is encrypted, the virus must start its execution by decrypting the viral body.

    The encryption that the virus uses is very simple. The key is always four bytes long, and the encryption scheme is always a simple xor.

    .DLL file insertion
    After the viral body is decrypted, the virus inserts a .dll file on the computer. It is this inserted .dll file that performs all of the malicious actions on the system. The .dll file is kept within the viral body in an encrypted state. Therefore, the virus must first decrypt the .dll file. After the .dll file is decrypted, it is inserted on the computer as C:\Rar$DI01.903 or as a random file name in the %system% folder.

    NOTE: %system% is a variable. The virus 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).

    The virus then executes this newly inserted .dll file. After the virus is executed, it jumps to the original entry point of its host program and allows the original host to execute.

    .DLL file actions
    The inserted .dll file is a keystroke logger and an IRC backdoor Trojan. It is also this .dll file that infects other PE files. It goes through all files on the system as it tries to find suitable PE files to infect.

    The inserted .dll file is multithreaded. This means that it can perform several different actions concurrently.

    Keyboard Logger
    The .dll file creates a thread that monitors all keystrokes. It logs the keystrokes in a file on the computer.

    IRC Backdoor Trojan
    The .dll file attempts to connect to an IRC server and join a chat room on that server. However, before it connects to the server, it attempts to bypass certain personal firewall products by creating registry keys that allow the communication.

    recommendations

    Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

    removal instructions

    NOTE: These instructions are for all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.


    For details on how to do this, read the following instructions.

    To update the virus definitions:
    All virus definitions receive full quality assurance testing by Symantec Security Response before being posted to our servers. There are two ways to obtain the most recent virus definitions:

    To scan for and delete the infected files:
    Reverse any changes that may have been made to your firewall
    If you suspect that your firewall software has been modified by the virus, check the product's settings, and change them to their original settings.

    Additional information:

    * What are Portable Executable (PE) files?
    PE files are files that are portable across all Microsoft 32-bit operating systems. The same PE-format executable can be executed on any version of Windows 95, 98, Me, NT, 2000, and XP. All PE files are executable, but not all executable files are portable.

    A common example of a Portable Executable file is a screen saver (.scr) file.

    Backdoor
    If the IRC Backdoor Trojan component was installed on the computer, it is possible that your system has been accessed remotely by an unauthorized user. For this reason it is impossible to guarantee the integrity of a system that has had such an infection. The remote user could have made changes to the system, including but not limited to the following:

    • Stealing or changing passwords or password files
    • Installing remote-connectivity host software, also known as backdoors
    • Installing keystroke logging software
    • Configuring firewall rules
    • Stealing credit card numbers, banking information, personal data, and so on
    • Deleting or modifying files
    • Sending inappropriate or even incriminating material from a customer's email account
    • Modifying access rights on user accounts or files
    • Deleting information from log files to hide such activities

    To be certain that your organization is secure, you must reinstall the operating system, restore files from a backup that was created before the infection took place, and change all passwords that may have been on the infected computer or that were accessible from it. This is the only way to ensure that your system is safe. For more information about security in your organization, contact your system administrator.


    Write-up by: Neal Hindocha