<null.TakeThisOut@zilch.com> to Michael Meier:
> >i hope, i'm right here.
> >im using f-prot -ws for linux, 2.4.18-4GB , suse 8.0 pro.
> >
> >F-PROT ANTIVIRUS
> >Program version: 4.3.5
> >Engine version: 3.14.8
> >
> >VIRUS SIGNATURE FILES
> >SIGN.DEF created 1 March 2004
> >SIGN2.DEF created 1 March 2004
> >MACRO.DEF created 23 February 2004
> >
> >i type this:
> >venezia:~ # f-prot -virlist | grep -i Netsky
> >Netsky.B@mm
> >
> >and i am wondering, because there is no Netsky.C@mm
> >nor Netsky.D@mm
> >only Netsky.B@mm ?
> >
> >Anybody knows, where is my mistake ?
>
> I have the same situation with F-Prot DOS. As of today, I know that
> F-Prot detects W32/Netsky.D@mm since I received a sample today.
> Yet the malware name is not included in F-Prot's /virlist
There was some internal confusion about the proper name for Netsky.D as FSI
detected a new Netsky around the same time as several other researchers. By
the time it was realized that this was not the same variant as everyone else
had been seeing, Netsky.D had become established as the name for the "other
Netsky" (i.e. not the one FSI saw) so FSI changed the name of its Netsky.D
to Netsky.E. The confusion surrounding this may have been present in the
..DEF update, depending on the time of its availability...
> There has been similar confusion with other malware along these same
> lines recently reported on the virus newsgroups. I don't know why the
> malware names of recent detections don't appear in the /virlist
This may, of course, be an unrelated issue. Maybe there is some resource
issue with older or commandline versions of the product??
--
Nick FitzGerald
FAQ
Profile
Private Messages
Log in
