This is a recurring issue with Palo Alto network devices. IPW software status communication from the target machine simply transfers information across your network through Port TCP 3121 back to the console. This process is a simple transfer of files and does not interact with your proxy. Our software does use existing OS components to run processes, and while we don't utilize it our self, our strongest estimation is that one of these processes takes advantage of the system32 IEProxy.dll. To support this information further, if you run a web search for Virus/Win32.WGeneric.rervj(2107546)reset-both code, you'll find a lot of false positive posts for Palo Alto devices specifically. Regrettably, we would not have a solution for Palo Alto components that trigger this error. I do apologize for the inconvenience but we would ask you to reach out to Palo Alto for further troubleshooting and obtaining an exclusion list for there components. I do hope you find this information helpful.
We are also experiencing the same threat alerts for ieproxy.dll during patch scans on DMZ servers. We have attempting to find the ieproxy.dll file on our servers but have not found one that is the same hash value.
We are also experiencing a similar issue with a file called "services.exe" that our Palo Alto is showing as a threat.
Any specific information on how shavlik utilizes these windows components or why they could be a threat would be beneficial. We are also reaching out to Palo Alto for further analysis and help tracking down the files on our systems.