Threat Descriptons



Category :


Type :


Aliases :

Korgo.F, Worm.Win32.Padobot.gen, W32/Korgo.worm.f, W32/Korgo.F


This Korgo (aka Padobot) variant was found in the very end of May, 2004. It is very similar to other Korgo variants. It 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:


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 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.

Technical Details

The worm's file is a PE executable 9728 bytes long packed with UPX file compressor. The unpacked file's size is about 15.8 kilobytes.

When the worm's file is run, it first deletes the FTPUPD.EXE file. Then the worm creates a mutex with the "uterm8" 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:

  • Windows Security Manager
  • System Service Manager
  • Bot Loader
  • SysTray
  • WinUpdate
  • avserve.exe
  • avserve2.exe

The key values are deleted from the following Registry key:

  • [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]

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:

  • [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
  • "System Restore Service" = "%WinSysDir%\<random>.exe"

where WinSysDir represents Windows System directory name and <random> represents random characters. The name of the worm's file can be for example 'jweisy.exe'.

Additionally the worm can create the following Registry key:

  • [HKLM\Software\Microsoft\Wireless]
  • "Client" = "1"

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.

Being active, the worm starts the IDENT server on TCP port 113. Additionally the worm can listen on random TCP ports. The worm doesn't listen on port 3067 like its previous variant, so it doesn't allow to upload and run files on an infected computer.

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.

The worm tries to contact the following IRC servers on port 6667:


If connection is successful, the worm joins the #stalin channel and creates a bot with a random name there.

More Support


Ask questions in our Community .

User Guides

Check the user guide for instructions.

Contact Support

Chat with or call an expert.

Submit a Sample

Submit a file or URL for analysis.