Is Kingsoft (Cheetah Mobile) flagging your website or file?
If Kingsoft (Cheetah Mobile) is flagging your site or a file — often showing up as generic malware/PUA detections (Kingsoft/Cheetah engine, e.g. Win32.Troj.* on VirusTotal) — 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 Kingsoft (Cheetah Mobile)
Kingsoft AV is now under Cheetah Mobile (CMCM); contact by email. Submit here: operation@cmcm.com (email)
- ZIP the sample (note any password).
- Email operation@cmcm.com with the VirusTotal link and exact “Kingsoft”/“Cheetah” label.
- Explain the false positive with publisher/build info.
- Request reclassification/whitelist.
- Follow up; expect slow replies.
Good to know: Kingsoft AV is under Cheetah Mobile (CMCM); operation@cmcm.com is the best-known contact but is not confirmed on an official page. Cheetah largely exited consumer AV, so support is minimal.
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 Kingsoft (Cheetah Mobile) 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.