Home > Threat descriptions >

Agobot.VS

Classification

Category: test

Type: -

Aliases: Agobot.VS, Agobot.VS, Backdoor.Agobot.VS, W32.HLLW.Gaobot, Gaobot, Win32/Gaobot, Phatbot, Phat

Summary


The Agobot.VS variant was found on October 27th, 2004. We received several reports about it from the field. This backdoor is functionality similar to previous Agobot variants.

Removal


Automatic action

Based on the settings of your F-Secure security product, it will either automatically delete, quarantine or rename the detected program or file, or ask you for a desired action.

Knowledge Base

Find the latest advice in our Community Knowledge Base.

About the product

See the manual for your F-Secure product on the Help Center.

Contact Support

Chat with or call an expert for help.

Submit a sample

Submit a file or URL for further analysis.

Technical Details


Security Updates

The most important step of disinfection is the installation of security patches for the vulnerabilities exploited by Agobot.

Detailed information and patches are available from the following pages:

Automatic action

Once detected, the F-Secure security product will automatically handle a harmful program or file by either deleting or renaming it.

More scanning & removal options

You can refer to General Removal Instructions for a simple guide on how to remove harmful programs.

More information on the scanning and removal options available in your F-Secure product can be found in the Help Center.

You may also refer to the Knowledge Base on the F-Secure Community site for further assistance.

Network Disinfection

For general instructions on disinfecting a local network infection, please see Eliminating A Local Network Outbreak.

Manual Disinfection

Caution: Manual disinfection is a risky process; it is recommended only for advanced users.

Manual disinfection of this Agobot variant requires killing the backdoor's process in memory and deletion of the infected file from Windows System folder.

The file name is 'winl0g0n.exe'. There are zeroes instead of 'o' letters in the file name: do not confuse this file with a Windows component named 'winlogon.exe'!