Is Panda flagging your website or file?
If Panda is flagging your site or a file — often showing up as Trj/…, PUP/…, Bck/…, W32/…, Generic Malware — it is either a real infection or a false positive from a past issue. Here is how to get it cleared.
Step 1 — Confirm it is really a false positive
Do not request removal while malware is still present, or the flag returns. Check first:
- Run my free Is My Site Hacked? checker.
- Cross-check on VirusTotal to see every engine flagging you.
If anything turns up, get it fully cleaned first — deleting the visible malware is not enough if a backdoor remains.
Step 2 — Report the false positive to Panda
Panda (now WatchGuard) handles endpoint false positives by email. Submit here: falsepositives@pandasecurity.com (email)
- Email falsepositives@pandasecurity.com with the flagged file and its detection name.
- Include the MD5/SHA-256 and why it is a false positive.
- Or open a case in the WatchGuard Endpoint Security console.
- Add a temporary exclusion in the endpoint console meanwhile.
- Await re-classification.
Good to know: Panda was acquired by WatchGuard (2020); endpoint AV false positives still use the falsepositives@/virussamples@pandasecurity.com mailboxes. WatchGuard’s web portal is for the network IPS engine, not Panda endpoint AV.
Step 3 — If the warning keeps coming back
A detection that returns after you have been cleared almost always means the infection was never fully removed — usually a backdoor in a theme file, a rogue admin user, or malware in the database. That is exactly what I fix. I am a USA-based WordPress security specialist: I remove the infection completely, submit the delisting on your behalf, and harden the site so it stays clean.
Get my site cleaned · See how it works · read my client reviews.
Frequently asked questions
How long does Panda take to clear a false positive? Once the site/file is genuinely clean and you have submitted the request, most are resolved within a few days. Submitting while still infected only restarts the clock.
It keeps coming back — why? Because the real infection (a backdoor, rogue admin, or database payload) is still there. A full cleanup stops the loop.