Thread-Log: Virus found

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Thread-Log: Virus found

L2 Linker

under our Threat-Log I found some Virus entries. The Attacker is an own PC from another vlan. We want to install windows updates over Ivanti-Patchmanagement with the original windows update service. And now the maschine, which we will patch, will do a virus attack - msiexec.exe and wscript.exe. Palo ID 194147259, Application ms-ds-smbv2...
We scanned both machines with a lot of tools and virus-scanner = nothing found!!!
Can somebody tell me the location of the infected files, which will shown in the thread log?
Have you some Tips for me?
Thank you verry much.



Accepted Solutions

Thank you for the samples. The issue is resolved and the signatures will be removed from tomorrow's release of Antivirus. In the future please report these type of issues by opening a case with Support.

View solution in original post


L3 Networker

To confirm this is on the firewall threat log? What was the action taken? If it droped or reset the session then traffic wouldn't have made it through to the host as it was blocked by the firewall.

I found that multiple Palo Alto Networks customers have reported this issue.


After investigation, I've concluded these are caused by signature collisions with a signature for malicious sample 7e3bdff41913aadc0f5e1e0cf65a9197a060ad68bd9196d92ee240e0ab702085.


I've submitted a request to fine tune the associated signature, so that it is less likely to produce signature collisions.


The issue should be resolved by Monday COB.

thanks for your responses 🙂
Did we talk about the same story?! How can I ensure that this virus message is a hoax or not?
At the top some Images about my virus troubles

How can I determine the directory of the affected file?


Thank you


Kind regards




Please upgrade to the latest Antivirus package and do let me know if you still see the signature triggering.

I tried to resolved this issue, but the msiexec.exe sample I had to work with was not triggering the signature collision any longer.

If yours continues to trigger after updating Antivirus, please locate the msiexec.exe file that triggers the signature, and share its sha256 hash with me.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!