Plans and safety
Malware findings and clean rebuilds
What the scan checks, what the findings mean and rebuilding a hacked site.
When scans run
- Before copying a connected site to staging, the live site is scanned on its server. Nothing is downloaded first.
- Before importing an uploaded backup, every file is scanned in a locked-down space before anything runs.
- Whenever you like: on the Security tab, press Scan for malware.
What the scan checks
- WordPress and wordpress.org plugins against their official files, to spot changes and extra files.
- Code, uploads and
.htaccessfor signs of infection. - The database, for injected scripts and suspicious content.
Premium and custom plugins can't be compared with official files; the results say which ones.
Reading the results
| Level | Means | Effect |
|---|---|---|
| High risk | Strong signs of malware | The site isn't copied, or the backup isn't imported |
| Suspicious | Worth a look; often harmless | Listed, doesn't block |
| For information | Notes, like leftover files | Listed |
A scan is a strong check, not a guarantee. If you think a site is compromised, treat it as compromised.
If your site looks infected
Don't send changes to it. The Security tab offers the safe way out: rebuild it cleanly on new hosting.
- Press Rebuild cleanly. A new site is created on your account.
- Only the old site's database content and its images and PDFs are taken, never its code. They're cleaned, and anything suspicious is removed and listed.
- The words and pictures appear in the new site's files. Tell us what to keep and what to change, then write the brief.
- The new site is built and goes live on fresh hosting, as with any new site.
Afterwards, close the old hosting account, or ask your host to clean it. Don't reuse it for the new site.