eScan / MicroWorld False Positive & Blacklist Removal

Is eScan / MicroWorld flagging your website or file?

If eScan / MicroWorld is flagging your site or a file — often showing up as generic malware/PUA detections (e.g. Trojan.Generic 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:

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 eScan / MicroWorld

Submit a sample/false-positive ticket to MicroWorld (eScan) support. Submit here: support.mwti.net ticket form

  1. Open the support ticket form.
  2. Select the “Samples / False Positive” department.
  3. Enter your name and email and describe why the file is clean.
  4. Upload the file (password-protect with “infected” if needed).
  5. Save the ticket ID and watch for the reply.

Good to know: The support.mwti.net form is the live 2026 channel; samples@escanav.com is the documented email fallback (fp@escanav.com is not confirmed on any official page).

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 eScan / MicroWorld 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.

Security Guides →