Re: win32\patched NAW Trojan... ESET please fix this fast - it is false positive. The file sfc_os.dll is patched with nLite to disable SFC....
in last couple of weeks i am seeing more and more of these nasty kryptik and rootkit(today it was rootkit.rustock .sys file in system32 dir)...
Well, I had similar case when Corporate license leaked out, but in correspondence with local ESET dealers, I was met only with arrogant...
Update: I moved all suspicious files with WinPe boot cd to one folder and scanned them with NOD32 (4053 database version). When scanned,...
I already did that about eight days ago. I submitted couple of those files with filenames similar to "ovfsthxusdgxcgv" created the same date. we...
Same thing here - on couple of machines in office, with installed v4.0.424 and configured for max protection and scanning, it only finds...
on October 2nd I manually submitted it for analysis via NOD32 GUI. Eight days later I was asked to submit via mail to samples@eset.sk finally...
well I just saw scrnshot on thread http://www.wilderssecurity.com/showthread.php?t=222304 and remembered that the same *virus alert* appeared to...
But this is not my first experience with NOD not detecting not-so-benign malware: -TrojanDropper.Agent.NHN -IRCBot trojan -AutoRun.GG worm...
Question: How is it effective if it doesn't detect at least as 'suspicious' something that does such major changes to system like completely...
Yesterday I googled Panasonic Cam "NV GS 17E driver" and downloaded file "Setup_ver1.1773.0.exe". XP SP3 and NOD32 v3.0.672 up-to-date and fully...
you see, I'm not pointing on improving AH by means of false positives and alike, but I'm pointing on what might be closed circle of AH missing...
well, you know what - since they were in quarantine, I could have restored them to some location and stop AMON from deleting(or getting back to...
in this case, however, it's not the whole system that was infected(it's my main work/home rig) but just that hd that I added to clean it, backup...
well maybe there is light in the dark hehe ie some files were sent to Eset for analasys as shown in pic. Threat Sense must be very helpful in this...
BitDefender scan was done AFTER NOD32 scanned/cleaned that whole drive. so it found what first didn't. and what it found doesnt seem like...
that's my thought too. too bad.
tnx Paul Wilders and dog.
as i said before, i have no intentions of flaming anything or anybody. it's true that it's not perfect, BUT why not try to improve it? is this...
and why wouldn't even that 6-8 viruser and 20-30 files they infiltrated, be cleaned by NOD? my intention was to, posibly, help in improving NOD's...
as i said, scaned disk is secondary and it had Win9x on it. beleive me, i do that on every XP machime i service. my rig is, for years now,...
and what's worse some of them are listed in NOD32 virus database. for example Win32/TrojanDownloader.Agent.FK. NOD32 v25.51.8 + MS AntiSpyware...
Separate names with a comma.