DM_HH

Thanks Marcos. I had created an exclusion, but wanted to check to see if there was any way for me to determine if there was any actual compromise. Would I need to look at every JS that is being called on the page when accessing one of these modules? Dan

Recently, while accessing certain content within the CP of our website, ESET has started detecting a "suspicious application" (JS/Packed.Agent.Q). This only appears when users with access to the control panel try to access the modules that allow for editing certain types of content. Our developer had installed a new plug-in somewhat recently, but has uninstalled it and the issue remains. We use a somewhat niche CMS (Expression Engine) and so it's difficult to determine exactly what JS or other component of the site is causing this potential false positive, as the URL for the content in question appears in the form of: "https://<websitedomainname>/<entryID>/<uniquesessionID>" rather than pointing to a path I'm able to follow or provide for analysis. If I tried to submit the path to the page for analysis, it would not be reachable. As far as I'm aware, the suspected threat is only detected when working in the backend, not when browsing the website itself. What is the best way for me to have ESET confirm if this is a false positive or if there is some problematic content on the site?