|Typical Symptoms||Security threats|
|Discovered|| [korea] 2009-03-26
|Scan engine needed||
2009-03-27 [Able to detect & repair]
[Symptom of Infection]
1. It creates files into below path.
(System Folder)WinHelp32.exe – Dropper.Agent.17408.S
2. This malicious code is registered to service for auto-executing on system reboot.
3. It tries to access to 222.XXX.XXX.206 server by using svchost.exe, but the remote server does not work.
4. Also, national ISP companies block the access to the remote server, thus user cannot access to the remote server.
5. This malicious code tries to connect continuously by adding ports because it cannot access to the remote server now. If, remote server works normally, the malicious code will control the infected system by malicious code's maker.
- "(System Folder)" could be different by system, and generally this is "C:WindowsSystem (Windows95/98/Me), C:WinntSystem32 (Windows NT/2000), C:WindowsSystem32 (Windows XP)".
[How to repair]
1. If you are WinXP/ME users, please be inactivate System Recovery Function.
The reason why being inactivate of the system recovery is to clean the virus completely.
You can refer to MS technical documents(Q263455) for more details.
2. Update the engine module for the latest one.
To repair this virus, you need to update the engine for the latest one.
a. ViRobot products users
-Download the latest engine files via our website (www.hauri.net)
b. Non-ViRobot products users
- Use the LiveCall (Free Scan) via the website (http://www.livecall.co.kr)
- Use the trial version of ViRobot products (30days only)
3. How to scan the virus.
a. Run your ViRobot, and choose "all files" in scan option.
- ViRobot Expert 4.0 : [Edit] -> [Configuration] -> [Scan] : Check all files
- ViRobot Desktop 5.0 : [Tools] -> [Configuration] -> [Virus Scan] : Check all files
- ViRobot Desktop 5.5 : [Tools] -> [Configuration] -> [Virus Scan] : Check all files
- LiveCall (Free Scan) : [Advanced Scan] : Check
b. Repair all viruses detected.
c. If [Auto-repair after rebooting] message shows up, please try to re-scan after rebooting the PC.