Hi there all,
I'm CyberMonitor, and as you can see, I'm new here on the forums. That aside, i've been a Norton Customer for a while and have mostly been satisfied with its performance and results until just recently.
I currently am using Norton Internet Security 2012, which managed to block the first attempt of a Fake Antivirus Virus Program (when I ran it by accident), but failed to stop all following iterations (there was at least one more, that I'm sure of...) afterwards. This Virus which I had downloaded originated from a .zip file, whose only contents included a "mypic.scr". Though I was suspicious of the whole thing from the outset, I was quite surprised that Norton didn't register the file and its subsequently created child files as threats, seeing as it was "supposed-to-be" a screensaver (.scr) file, which would NOT fit any of its registered or taught file extension recognizations. It didn't even say so even after it started to take effect, even after running individual file scans!
After many hours, and with whatever computer expertise I had, I managed to remove almost every element of the Virus myself, with some of Norton's help. It was a miracle that the Virus didn't have enough complexity and sophistication to take down Norton the whole time.
So, while I stil have some faith in Norton, I would like to help improve Norton's definitions and handling of such threats, especially new ones that have not been dealt with as of yet. Hence, I would like to know where I may be able to submit the source, or at least the source file so that the guys at Symantec can help us help themselves handle it.
I still have the original email in which I could download that digital monster again (but of course, would rather not to), I would like to submit it for investigation, because nothing beats an actual SOURCE which one could reverse-engineer and defeat it. I have more specific details and observations about this one Virus in particular, but do not have the time to entail about them.
Awaiting Your Replies of Support,
-CyberMonitor.