Is Cybereason flagging your website or file?
If Cybereason is flagging your site or a file — often showing up as generic malware detections (the “Cybereason” engine verdict 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 Cybereason
Cybereason has a dedicated VirusTotal false-positive mailbox. Submit here: vt-feedback@cybereason.com (email)
- Email vt-feedback@cybereason.com.
- Include the exact VirusTotal URL/hash showing the Cybereason verdict.
- Attach or link the file if possible.
- Explain why it is a legitimate, non-malicious file.
- Request removal of the detection from their VT feed.
Good to know: Independent US/Israeli EDR vendor; the vt-feedback@ alias is specifically for VirusTotal-engine feedback (the on-prem product uses a separate in-console workflow).
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 Cybereason 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.