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.
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.
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.
Take a look on my uploaded image, please.
I don't unterstand this....
On the Victim Machine we scan the attacker with a patchmanagement software. No login on the attacker machine!
Why does the palo shows urls unter the file name?! We also scanned the victim machine with different anti virus software as TrendMicro and Kaspersky - nothing found!
I hope you have any ideas?
Thank you 🙂
The URL's in the file names looks like a product defect. If I remember correctly, it is caused by limitations with the SMB decoder, which by the way has been significantly improved in PAN-OS 8.1. I would focus my attention on resolving the collision though. Have you been able to spot the msiexec.exe file causing the signature to trigger?
They weren't false positives. False positives are when WildFire gives a Benign file a Malicious verdict.
In this case, WildFire gave the files a Benign verdict, but they were triggering Antivirus signatures. We call these Signature Collisions. These happen when the digital patterns that the firewall looks at to identify a file, concide between a Benign sample and an Antivirus signature that has been generated from a Malicious sample that is similar in structure to the Benign file.
You can read more about these at:
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!