Disable iTunes Trojan Horse Small.Bog False Alarm by AVG
Users who are using AVG anti-virus might have been alerted by the security expert that their iTunes program is infected by virus. A malware named Trojan horse small.bog is purportedly identified and detected hiding in iTunes files by the AVG antivirus after users have updated their latest virus definitions. As a security measure, AVG will quarantine these infected files and prevent iTunes from working. Apparently this security alert is a false alarm triggered by the famous free antivirus software. AVG has made a howler by identifying iTunes files as a Trojan horse. This error only happens when users are using the AVG Antivirus Free edition. If users are running the full AVG Security Suite or other antivirus programs such as Norton Antivirus, McAfee, etc, there is no alarm triggered.
Other than creating confusion amongst users, the false alarm, Trojan horse small.bog, doesn’t really jeopardize users’ systems. Users can disable the false alert by creating an exception in AVG:
1. Open AVG
2. Go to Resident Shield -> Manage Exceptions -> Add Path
3. Add C:\Program Files\iTunes and C:\Program Files\iPod
Related Articles
- False Alarm From AVG To Flag Free Firewall ZoneAlarm As A Security Threat
- Remove False Alarm PC Defender 2008
- How to Clean and Remove Trojan.Win32.Obfuscated.gx, Trojan.Win32.agent.akk, Trojan.Zlob and Etc.
- Google Adsense Infected by Trojan.Qhost.WU
- Filterbit Free Online Virus Trojan Spyware and Malware Scanner: Single Upload File Scan with Multiple Security Products
- Don’t Get Infected by Trojan.Zlob When Browsing Edison Chen Sex Scandal Photo
- iTunes Give Away Free Media Via iTunes 12 Days of Christmas
- Download Free iTunes 9 With Innovative Features (iTunes LP, Home Sharing And Genius Mixes)
- Web-Based MetaClock Alarm To Wake You Up
- Greet the Day With Finger Dance Alarm Clock
Entries (RSS)
July 26th, 2009 23:51
i dont really think it is “completely” the mistake of AVG. Antivrus programs try to predict whether there is an unknown virus in our system and that depends on the kind of code in a binary. Code written by programmers should be such that it doesn’t trigger the security features of any system. So in my opinion, this should be dual responsibility.
That said, it could be possible that this is indeed AVG’s blunder. But fixing responsibility without knowing the internal details should not be done.