It is really hard to say that does avast! has this virus in it’s detection libraries, since same viruses might have different aliases on different Antivirus vendors.
In all eight AVs detected it and not one has used the same name, with only one using W32/Nopir-B for the name so you might reverse the logic and ask why they used that as the majority have used a name with either P2P or VB in the name.
This is not just an avast but industry wide problem with no standardised naming convention.
Why do we need VGrep?
We need VGrep because, without the correct name, it may prove very difficult to access accurate information about a virus and its effects.
Virus names are so confused for two reasons - the nature of the viruses themselves and the way in which the anti-virus industry works.
The first is perhaps the most obvious - many viruses have nothing particularly unique about them, which can make naming them rather difficult.
The second point is probably more important, however. When an anti-virus company receives a sample of a new virus, its primary objective is to incorporate detection of that virus into its product. The virus researchers don’t have time to worry about what to call it immediately, so they instruct the product to refer to it as (for example) ‘Fred’. Later, they may conclude that the virus should, in fact, be called ‘Jerusalem.Australian.Fred.1089’. Many companies change their products accordingly, however there remains a great deal of confusion.
VGrep allows simple cross-referencing between some of the more popular AV products.
VGrep is a great tool however, it is not so useful for new viruses as it takes a little time to get listed in the database. So it is not unusual to find no reference of the latest viruses.