This Korgo (aka Padobot) variant was found on June 17th, 2004. It is a bit modified comparing to previous Korgo variants. Korgo.P worm spreads throughout the Internet using a vulnerability in Microsoft Windows LSASS. A description of the vulnerability can be found in Microsoft Security Bulletin MS04-011: https://www.microsoft.com/technet/security/bulletin/MS04-011.mspx
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.
The worm's file is a PE executable 9343 bytes long packed with a modified UPX file compressor. The unpacked file's size is about 19 kilobytes.
When the worm's file is run, it first deletes the FTPUPD.EXE file. Then the worm creates a mutex with the "uterm13" name. This is done to avoid loading multiple copies of the worm into memory.
Next, the worm deletes Registry key values and terminates processes with any of the following names:
The key values are deleted from the following Registry key:
After that the worm installs itself to system and creates a startup key for its file in the Registry. The worm's file is copied to Windows System folder with a randomly generated name. The following Registry key is then created:
where WinSysDir represents Windows System directory name and <random> represents random characters. The name of the worm's file can be for example 'sjsudf.exe'.
Additionally the worm can create the following Registry key values:
The worm tries to start its spreading routine as a remote thread of Windows Explorer. If this fails, the worm starts the spreading thread directly.
Unlike its previous variants, the worm does not connect to IRC, does not create an IDENT server on port 113 and does not start a backdoor on port 3067. Instead, the worm periodically connects to several websites (sometimes, depending on an internal flag, with a specially constructed URL) and reads a file from there. If the file's data does not contain 'zer0' string, the worm waits and re-connects again. But if the file contains 'zer0' string, the worm downloads an executable file from that website to Windows System folder and runs it. It should be noted that the worm performs a secure authentication before the file is downloaded.
Here's the list of websites that the worm tries to connect to:
Additionally the worm can listen on a random TCP port.
The worm spreads to remote computers using LSASS vulnerability. It contacts remote computers on TCP port 445, exploits the vulnerability and copies its file to a remote system.