Allow F-Secure Anti-Virus for Windows Servers to disinfect the relevant files.
For more general information on disinfection, please see Removal Instructions.
Worm:W32/Morto.A can be viewed as having three components: the dropper, the loader, and the payload.
Upon execution, it sets the data of the registry value HKLM\SYSTEM\WPA\ie to its own full path, then deletes the registry key, HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU.
It then saves a copy of the embedded encrypted data to the registry value, HKLM\System\Wpa\md. This encrypted data is actually the payload of the malware.
It then drops a DLL component in the Windows directory named clb.dll (which is the loader) and executes regedit in the Windows run command, then terminates.
The clb.dll or the loader gets triggered when the regedit command was executed. This happens because regedit normally loads a normal Windows DLL component from the %systemdir% folder named clb.dll. Due to the nature of the Windows DLL loading mechanism, the clb.dll file that was dropped by the malware in the Windows directory gets loaded instead of the one in the %systemdir% directory.
As it is the malicious DLL that gets loaded, the regedit command does not show any graphic user interface (GUI) as it normally does. It decrypts and loads the encrypted payload saved at HKLM\System\Wpa\md registry value. This is when the payload takes control.
It renames clb.dll to clb.dllbak so regedit will execute as normal and will not appear to be suspicious to the user.
When the loader is triggered by rundll32.exe, it tries to read the following file-like objects: \\tsclient\a\moto and \\tsclient\a\RIR1.
The malware also does the following modifications:
The payload contains the self propagating mechanism of the malware. It does this by brute-forcing the administrator login to Remote Desktop Services (TCP port 3389) using a set of passwords embedded to the binary. It does this on the computers connected to the local subnet.
On successful login, it will attempt to copy and execute the loader component and a registry file to the server, with the names \\tsclient\a\a.dll and \\tsclient\a\r.reg, respectively.
The registry file contains these entries:
Since the loader is expecting rundll32.exe to trigger itself, this seems to give the rundll32.exe Administrator rights, as well as the loader.
The malware also monitors processes related to antivirus and security software and terminates them if the following strings are found:
The malware also attempts to communicate to ss.qfsl.net, test.qfsl.net: 1031, and 184.108.40.206:80 probably to report, wait for commands, or get some updates.