Some small problems with avast

[igor0]

@Qianwenxiang post:1

I found some small problems with avast when i use it , like:
1/a place not completely translated to Chinese like “malware type : exploit”(see 0b.jpg) and "exploit "should be “漏洞利用” in simplified Chinese version.

As far as I know, these “virus types” (exploit, and there was one more I think) were added into avast! shortly before the release, so I didn’t send the translation packages to the translators, as most of them wouldn’t come back in time anyway. So yes, this word is not translated, in most of the languages.

@Qianwenxiang post:1

2/When i use avast to scan a lot of virus samples it may sometimes warns me “Instruction at 0x7c936f1c referenced memory at 0x0000000 the memory could not be read” .

I would need to take a look at the samples causing the error. The problem is that the actual error might be caused by one file, but the error actually appears later during the scan (if you’re saying that you are scanning a big number of samples). So, if you could somehow find out which file causes the problem (by scanning only some of the samples and making sure the error appears… possibly by dividing the samples into smaller group) - and if you could send me the problematic file (or even an archive full of files - if this archive reproduces the problem), it would be great.
I’d certainly like to fix the problem, but I can’t do it without the file(s) to reproduce the problem.

@Qianwenxiang post:1

3/When avast scans a file packed by some strange packers avast may say "complete scan,but found some internal error "

Again, please can you send us the files? I’d take a look at them as soon as possible. (Or, if the files are many or huge, you can upload them to ftp://ftp.avast.com/incoming) Thanks.
I am certainly looking for this kind of errors, but none appears on our (huge) collections, as far as I know. So, any samples causing these problems are welcome.

@Qianwenxiang post:1

4/avast could not detect a virus that packed by packer named “nakedpack” (like a file on my computer , when it didn’t packed by naked pack avast reports it as “Win32:Spyware-Gen [Spy]” and when it packed , avast reports “No malware”)

There are hundreds of packers that avast! (and also many other antiviruses) can’t unpack. So, why are you worried just about NakedPack?
Actually, the unpacker for NakedPack has been added in the last avast! update (4.7.1043) - but the unpacker is somehow incompatible with “-Gen” detections (Trojan-Gen, Spyware-Gen, etc.). So, if you repack the file detected as Trojan-Gen with NakedPack, in won’t be detected indeed (but, you have just created a new malware variant; if this variant gets in the wild, we’d add another detection for it).
To fix this “incompatibility” between the unpacked and -Gen detections, the detection algorithm would have to be changed - which is planned, but will require a big change to the VPS, so will most likely happen in avast! 5.