![]() |
NOD32: File scanning borked?
This happened several weeks ago, but I was wondering if anyone could tell me what happened. I was browsing those stupid warez sites trying to find a keygen for a program of mine, and hesistantly I downloaded some .exe that I thought were a keygen for the program (later I found just a page with the serial on it, so didn't need to download a program, but I digress). Goddamn warez and crack sites, those scumbag motherfuckers.
Anyway, before I open the file I make sure to scan it with my NOD32 program, so I right-click on the file and click on the NOD32 option, and it scans the file. It doesn't bring up any messages about it being a virus or whatnot, so I go ahead and open the file, and that's when another part of NOD32 pops up (AMON - File system monitor) and says, hold on there buddy, this is a trojan virus, so we've automatically quarantined it for you without actually running it. So my question is how come the initial virus scan on the program didn't come up with any warning that this was a virus? When I used to have Norton Anti-Virus usually when I scan files it would tell me whether or not it was a virus or not, so I didn't have to risk opening the file. I'm glad NOD32 has this file system monitor apart of its program, but it does make me a little more jumpy opening suspected files. Any ideas what's going on? It's a good program though. |
Maybe NOD32 didn't have that specific virus in its definition file but caught it trying to do sketchy things when you tried to open it and caught that. NOD32 is supposed to have the best heuristic scanning so that sounds right to me.
|
Quote:
|
Quote:
Code:
ÜÜÜ |
Quote:
|
Thanks for the link. The version that I downloaded was off some torrent and all I had to do was replace three files with the cracked files, and it seems to be working out properly. It's been updating itself regularly and I haven't had any messages about the trial running out or anything, so I think it's working just fine, but not 100% sure since T1249NTSCJ said something about how it might be ineffective, not sure what he was talking about really.
|
Yea, Nod32 doesnt need any cracking, just that fixer app that fixes your trial time to 239829829 days.
I have no idea why the initial scan did not pick up the virus. Perhaps you need to set something so the manual scan is more indepth? Or, it could be possible that this specific virus was not in the virus definitions. Nod32 has very powerful heuristics so it can detect a virus not in the database yet. That's a possibility. |
All times are GMT -5. The time now is 03:18 PM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2025, vBulletin Solutions, Inc.