Jump to content
chen

Samples Analysis Issues

Recommended Posts

I recently put a large number of samples compressed into the ZIP file submitted to immunet do analysis.

I found a few things I would like to not understand 1. Immunet can be detected containing a large number of samples ZIP file.

2. Decompress containing a large number of samples ZIP file, immunet can not be detected.

For example

10 samples were compressed into a zip file, and named 123, 123 zip file submitted immunet ,immunet detected 123 zip file as a virus, but the 123 zip file inside the 10 samples decompress ,use immunet to go scan ,immunet judged clean.

 

In addition, the problem if you do not fit in the version of the district to discuss, please forgive me, because I do not know where to put the problem.

  • Like 21

Share this post


Link to post
Share on other sites

Hi ryuusei, could you go into Scan Settings and see if Scan Archive Files and Scan Packed Files is turned on or off? Also what is the name of the detection so we know which module is detecting the zip file.

Share this post


Link to post
Share on other sites

Q:Scan Archive Files and Scan Packed Files is turned on or off?

A: on

Q:Also what is the name of the detection so we know which module is detecting the zip file.

A:has been detected as rogue:VLHJO-tpd.

quarantine was successful

Share this post


Link to post
Share on other sites

Immunet does use "heuristic" detection methods. This way Immunet can detect and react to unknown and unseen threats. I believe that's what's causing the zip file to be flagged as malicious while the samples themselves do not since they're not yet in the cloud database.

Share this post


Link to post
Share on other sites

I believe it is the TETRA module that detected the zip file with the information you provided. Here is some info on detection names I found from an older thread:

 

How do you know which engine detected the file?

* if the virusname starts with "W32." then it is a cloud detection

* if it starts with "W32.SPERO.", it is a cloud detection from the SPERO heuristic engine

* if it starts with "W32.ETHOS.", it is a cloud detection from the ETHOS heuristic engine

* if it starts with "W32.Clam.", it is a file that was detected by ClamAV on the cloud

* if it starts with "Clam.", it is a local ClamAV detection

* if it starts with "Clam." and ends with ".UNOFFICIAL", then it is your custom signature

 

If one or more of those samples were indeed rootkits or something similar to rootkits I could see where the heuristic functionality of the TETRA engine would detect the zip file and quarantine it even though the cloud or ClamAV engines did not because the detection signitures do not yet exist for those engines.

 

Regards, Ritchie...

Share this post


Link to post
Share on other sites

Hi

Thank you for the description, but I use the free version, so I can not start the TETRA engine detection,so this should not be TETRA engine caused, There may be other causes the generation of a problem.

Share this post


Link to post
Share on other sites

If you're using the free version it definetly isn't the TETRA module detecting the zip file then. Mmm. It's one of the other engines causing this but I'm at a loss as to which engine it is. I hope a support person reads this topic and can further help you.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×