Had a client with a system that was infected with an new strain of malware. It was identified as Trojan.Win32.Genome.arbx and was infecting the svchost.exe.<\/p>\n
The system was running Windows XP Kaspesky Antivirus 2011. The client complaint was that the system had been locking up and running slow. Initial contact with the system was remotely.\u00a0 Initial check show that the Kaspersky was was running and the database were up to date.<\/p>\n
I checked\u00a0 the task manager and found 6 iexplorer processes running without a user interface. Attempts to kill the process would restart a new process.\u00a0 I updated Malwarebytes, Ran a scan and found 155 infected objects, deleted those objects and restarted the system.\u00a0 After the reboot, Kaspersky popped a message stating the svchost.exe was infected with the Trojan, and in would only allow it to be ignored.<\/p>\n
I checked the task manager and the iexplorer processes were still running.\u00a0 I check the setting in Kasperky and found the the setting to ignore the svchost.exe removed it from the expetion list, only to have it return.<\/p>\n
Ran Malwarebytes full scan and did not locate any malware. At this point I shutdown the system and told the client I wold pickit up when I got back into town. I picked up the system and took it to the office I ran my tools in safe mode and did not find the malware.\u00a0 I finally did a repair install of WinXP that got rid of the trojan.<\/p>\n
After patching the system. Kaspersky would not start it protective services on boot, I had to start them manually. I tried updating to 2012 and still had the same problem. I finally un-installed Kaspersky and scrubbed the registry and residual\u00a0 keys, after reinstalling everything was working properly.<\/p>\n","protected":false},"excerpt":{"rendered":"
Had a client with a system that was infected with an new strain of malware. It was identified as Trojan.Win32.Genome.arbx and was infecting the svchost.exe. The system was running Windows XP Kaspesky Antivirus 2011. The client complaint was that the system had been locking up and running slow. Initial contact with the system was remotely.\u00a0 […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[24],"tags":[51,50],"class_list":["post-222","post","type-post","status-publish","format-standard","hentry","category-windows","tag-kaspersky","tag-malware"],"yoast_head":"\n