Is VBA32 (VirusBlokAda) flagging your website or file?
If VBA32 (VirusBlokAda) is flagging your site or a file — often showing up as BScope.Trojan.*, Backdoor.Agent and similar heuristic/“BScope” labels — 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 VBA32 (VirusBlokAda)
VBA32 (VirusBlokAda) is email-only. Submit here: feedback@anti-virus.by (email)
- Email feedback@anti-virus.by (or newvirus@anti-virus.by).
- Attach the file (zip if blocked) and quote the exact VBA32 detection name.
- Explain why it is clean and add a VirusTotal link.
- Write in English to support-en@anti-virus.by if needed.
- Replies are typically fast, with the fix in the next update.
Good to know: Email-only; Belarus-based vendor. Both feedback@ and newvirus@anti-virus.by are active.
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 VBA32 (VirusBlokAda) 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.