There is no optional operation for decompression bomb in AVAST. Understanding that in some cases, decompression bomb may do no harm, I suggest to add optional operation for it cos it can possibly be malwares.
Also, about submission from virus chest.
Bulk submission function, i.e. submitting more than one file at one time, is suggested.
If I have many samples to submit, it’s very tiring to select a file for submission on by one.
In all honesty why would you want to even consider scanning it, when it is an inert archive file.
Archive (zip, rar, etc.) files are by their nature are inert, you need to extract the files and then you have to run them to be a threat. Long before that happens avast’s Standard Shield should have scanned them and before an executable is run that is scanned.
Thank you. I know archive files are inert. I ask because I seemed to find a non-archive file identified as a decompression bomb by AVAST. And that file was detected as a malware by other AV. So I surmise if AVAST can remove decompression bomb, it may improve security level.
Since you don’t give any examples of the file/s considered as a decompression bomb (file name and file type), I can’t comment on that.
The decompression bomb name is not an indication that it is infected, just that it hasn’t been scanned as to do so would require extraction and that would be very large.
The file that is first opened 0723-easy_life(57).exe is essentially an archive, a compressed installation executable (which is an exception to archives being scanned). The |> bit after the 0723-easy_life(57).exe name indicates that this is more than a single file and there is another executable update.exe which may also be a large file.
Presumably this is something which you downloaded (and from where) ?
Given that it is in a temp \desktop\temp\ location and the VT results believe it to be infected it could be removed manually) ?