How to quarantine, restore or delete infected files

For server administrators · Updated 2026-10-29

On this page
  1. Steps
  2. Good to know
  3. Common questions

Every file the scanner or the file watcher finds is listed under Detected files. You decide what happens to it.

Steps

  1. In the administrator panel (https://<server>:2087), open Malware Scanner (section Security).
  2. Under Detected files, find the file. The File column shows its path in the account (~/ is the account's home), Threat shows what was found.
  3. For a file with the status found, click:
    • Quarantine — the file is moved out of the website into quarantine. The website can no longer run it.
    • Ignore — the finding is closed and the file stays where it is.
  4. For a file with the status quarantined, click:
    • Delete — the file is deleted permanently (you are asked to confirm).
    • Restore — the file is put back in its place. Do this only for a false positive.

The list shows open findings. Click Show history to see all of them, including deleted, restored and ignored ones; Show open only goes back.

Good to know

  • Quarantined files are kept in /var/quarantine/sahaab/ on the server, readable only by the system, until you delete or restore them.
  • Restore puts the file back at its original path with its original permissions, except that group and others can no longer write to it.
  • Ignore is not permanent. An ignored file is reported again by the next scan, or by the file watcher when the file changes. If it is a false positive, that is expected; if it keeps coming back, check the file.
  • A quarantined file can break a website if a real part of the site was infected (for example a plugin file with injected code). Reinstall the plugin or theme, or restore a clean copy from a backup.
  • Customers see the findings on their Security page (a quarantined file is shown as isolated). They cannot act on them.

Common questions

How do I know if a finding is a false positive?

Open the file in the File Manager of the account (or over SSH) and look at it. Code that decodes and runs hidden text (eval(base64_decode(…))), runs what a visitor sends (eval($_POST[…])), or a .jpg or .ico that contains PHP is almost never legitimate.

The infection came back after I deleted it. Why?

The hole the attacker used is still open, or a backdoor elsewhere recreates the file. Update the application, its plugins and themes, change all passwords, and run a full scan of the account.

Should I turn on automatic quarantine?

It stops infected files at once, day and night. The risk is a website that breaks because a real file was quarantined. Many hosts turn it on and restore the rare false positive.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.