A remote administration tool (RAT) that bypasses the security features of a program, computer or network to give unauthorized access or control to its user.
Based on the settings of your F-Secure security product, it will either move the file to the quarantine where it cannot spread or cause harm, or remove it.
A False Positive is when a file is incorrectly detected as harmful, usually because its code or behavior resembles known harmful programs. A False Positive will usually be fixed in a subsequent database update without any action needed on your part. If you wish, you may also:
Check for the latest database updates
First check if your F-Secure security program is using the latest detection database updates, then try scanning the file again.
Submit a sample
After checking, if you still believe the file is incorrectly detected, you can submit a sample of it for re-analysis.
NOTE If the file was moved to quarantine, you need to collect the file from quarantine before you can submit it.
Exclude a file from further scanning
If you are certain that the file is safe and want to continue using it, you can exclude it from further scanning by the F-Secure security product.
Note You need administrative rights to change the settings.
This malware installs a rootkit onto the system. In addition to hiding its presence on the system, the rootkit is able to inject a dropped file into a process, which is then able to function as a backdoor program.
During installation, this malware creates a copy of the file %System%\ADVAPI32.DLL as:
It then modifies this file with 21 bytes at the entry point, in order to load the file %Temp%\TDSS%randchar1%.tmp. A number of additional changes must take place for this to occur.
First, the malware deletes the "\KnownDlls\advapi32.dll" section object of the Windows Operating System, in order to remove the legitimate advapi32.dll. The section object is then recreated and linked to the %Temp%\TDSS%randchar2%.tmp file. It then stops and restarts the "MSISERVER" Windows service, which subsequently loads the %Temp%\TDSS%randchar2% file.
The cumulative effect of these changes causes %Temp%\TDSS%randchar1%.tmp to be loaded as a Windows service, which then creates a file, %systemdir%\drivers\TDSServ.sys. This sys file is the actual rootkit driver file. The rootkit hides all its files, as well as registry components beginning with the string 'TDSS'.
The loaded rootkit driver then drops a dll file in the %systemdir% as "TDSSl.dll". It injects the dropped file into SVCHOST.EXE and tries to connects to a number of websites, which are still live at time of writing.
The injected dll can also function as a backdoor, which may be commanded to perform any of the following routines:
Creates these files:
Creates these mutexes:
Attempts to connect with HTTP to:
The rootkit driver is registered with the key:
It may also create the following registry subkeys:
The malware creates the following registry entries:
A mutex is then created so that only one copy of the malware will reside in memory at any given session.