Is Baidu flagging your website or file?
If Baidu is flagging your site or a file — often showing up as generic malware/PUA detections (Win32.Trojan.* via the VirusTotal “Baidu” engine) — 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 Baidu
Baidu is email-only; its old web form is dead and the consumer AV is discontinued. Submit here: bav@baidu.com (email)
- ZIP the flagged file (note any password).
- Email bav@baidu.com with the VirusTotal link and the exact detection label.
- State it is a false positive and request whitelisting.
- Attach the sample or a build URL.
- Follow up at gaoyingchun@baidu.com if no reply.
Good to know: Email-only and slow — Baidu’s consumer antivirus is discontinued and the old web form (antivirus.baidu.com) is dead. The engine still appears on VirusTotal.
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 Baidu 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.