🇫🇷 Marseille Cloud VPS is live. One more place to put your sites. 70% off your first month with code GOMARSEILLE70 Get Yours →

WordPress Malware Removal & Hacked-Site Recovery: The Host-Level Playbook

Category : Wordpress
By :SVWebTeam
Nov 16, 2026

A hacked WordPress site needs a recovery sequence: contain the incident, preserve evidence, find the affected files and accounts, then restore or clean the site and close the entry point. Deleting the first suspicious file or restoring yesterday’s backup can leave the cause in place.

This host-level playbook helps site owners and administrators decide what to check themselves and what to ask their hosting team. Redirects, unknown administrators and server-load spikes are useful clues, but none identifies the full scope of an incident on its own.

🚀

Site hacked?

SiteValley Pro Web Hosting

Prepare for recovery with web hosting that includes daily backups, Imunify360 protection and a 24/7 support team.

Imunify360 protection
Daily backups
24/7 support
60 recovery points

Contain the Incident and Preserve Evidence

If visitors are being redirected, shown phishing content or exposed to malicious downloads, ask your host to restrict public access while recovery proceeds. A server-level restriction is more dependable than a maintenance plugin running inside a compromised WordPress installation. Record when the symptoms started, affected URLs, recent deployments and any alerts before making changes.

From a device you trust, secure the accounts that control the site: hosting, WordPress administration, SFTP/SSH, email used for password resets and, where relevant, the domain registrar. Revoke unknown access and enable multifactor authentication where available. After cleanup, rotate credentials again if they could have been exposed during the incident.

Keep a separate copy of the current files, database and available logs, clearly marked as potentially infected. Store it outside the public web directory with restricted access. It may help identify the entry point or recover legitimate recent content; it is not a clean restore point. The official WordPress hacked-site guidance also recommends documenting the incident and contacting the host.

A useful support request includes:

  • The exact site, affected URLs and first observed time, including time zone.
  • Any scanner finding, suspicious file path or unfamiliar administrator account.
  • The latest known-good backup date and whether orders or submissions arrived afterward.
  • A request to preserve logs, check other sites in the account and explain the available restore scope.

If the hosting account itself is compromised or access keeps returning after cleanup, involve the host or an incident-response specialist before reopening the site.

Match the Symptom to Evidence

Investigation guide: redirects need file and database checks, unknown administrators need account and access-log checks, and server load needs process and request checks.

Use the symptom to choose the next check, rather than treating it as a diagnosis. Record what changed and compare it with a known-good version or a trusted vendor package.

Symptom Evidence to inspect Avoid assuming
Unexpected redirects or injected links Rendered pages, rewrite rules, theme/plugin files and database content Every redirect comes from one file
Unknown administrator or spam accounts Account roles, recent access, registration settings and audit logs if retained Every unfamiliar username is malicious
White screen or PHP error Private PHP error logs and recent code or version changes A fatal error proves malware
High CPU or outbound mail Processes, request logs, scheduled jobs and mail logs available to the host A busy server proves cryptomining

Redirects may depend on the visitor’s device, referrer or login state. Give support reproducible URLs and conditions, without opening suspected malicious destinations unnecessarily. For unexpected users, verify ownership first; preserve the relevant records before removing confirmed unauthorized access.

For a broken site, use the host’s private error log first. If debugging is necessary, follow the WordPress debugging documentation: keep errors off public pages, protect the log location and disable temporary logging afterward. Public debug output can expose file paths and other sensitive details.

Use Scanners for Different Parts of the Investigation

A WordPress file scan, a public-page scan and a hosting-level scan answer different questions. The official website captures below identify the tools; they are marketing-page evidence, not screenshots of tests performed on your site.

Wordfence: Check the WordPress Installation

Official Wordfence desktop homepage with the Wordfence logo and its WordPress security headline.

Wordfence’s scanner can inspect the WordPress installation for suspicious files, malicious code and other issues. It is useful when the application remains accessible, but a compromised server or missing permissions can limit what an application-level tool sees.

Read each finding before acting. Wordfence can compare supported core, plugin and theme files with repository versions and offer repair where an original is available. Premium, custom or unavailable packages may need clean copies from their actual developer. Its scan-result documentation explains why modified files and unknown files need different handling. Preserve custom changes before replacing anything, and do not treat every difference as confirmed malware.

The free edition has delayed malware-signature and firewall-rule updates compared with Premium. Choose the service and update level appropriate to the incident; installing a plugin alone is not a complete recovery plan.

Sucuri SiteCheck: Inspect the Public Pages

Official Sucuri SiteCheck desktop homepage showing Sucuri branding and the website malware and security checker heading.

Sucuri SiteCheck is useful for checking what an external visitor can see: exposed malicious code, suspicious redirects and reported blocklist status. It can complement an internal scan, especially when a compromised site looks normal to a logged-in administrator.

Its access is limited to the public site. A clean result does not establish that private files, scheduled tasks or the database are clean. Use it as one check alongside file and account investigation, and retain the URL and time of any finding so you can compare it after repair.

Imunify360: Coordinate Host-Level Cleanup

Official Imunify desktop homepage introducing Imunify360 as an automated web server security platform.

Where the host provides it, Imunify360 adds a server-level view. The official user-interface guide describes file findings and scan history, with actions that depend on the host’s configuration. Ask which directories and accounts were scanned and whether the result records a detection, cleanup or removal.

Review the affected path and history before taking action. Cleanup can remove malicious content; deleting a file can also break a legitimate plugin or theme. Restoring an original from a cleanup backup can reintroduce the infection. An ignore-list entry is not a repair and can exclude a file from later scans.

SiteValley’s web-hosting page lists Imunify360 protection. Confirm available controls and the scope of assistance with support rather than assuming every customer sees the same interface or that an alert guarantees the whole account is clean.

Choose a Backup Without Losing New Orders

AI-generated conceptual photograph of a hand beside an external drive labeled Recovery Copy, illustrating a separately preserved backup.

Select a backup that predates the earliest evidence of compromise, not simply the latest visible symptom. Test it in an isolated recovery environment before replacing the live site. A backup can contain the same vulnerable plugin or stolen credentials that allowed the incident.

The WordPress backup guidance distinguishes database content from website files. You need to know what each restore point actually contains and whether those parts belong to the same working state.

Restore scope What it may recover What to protect first
Files only Core, plugins, themes and uploads included in that copy Legitimate file changes; investigate database changes separately
Database only Content, settings and application records from that time New orders, accounts, submissions and incompatible file versions
Full account or site The components included by that backup system Everything created since the restore point; confirm email and other-site scope

For a store, pause new transactions during the agreed recovery window and reconcile recent orders against trusted payment and business records. Do not blindly import the entire compromised database into a clean installation. Ask a specialist to recover legitimate records selectively when you cannot separate them safely.

In cPanel, the Backup Wizard documentation distinguishes partial restores from full-account restoration, which requires the server administrator’s tools. Your provider may use another backup system, so confirm the procedure before clicking Restore.

Repair the Site and Close the Entry Point

Whether you restore a backup or clean the current installation, keep the site restricted until the affected components and access paths have been reviewed. Replace compromised software with authentic packages, preserve legitimate custom work and update or remove the vulnerable component. A visible repair is incomplete if an attacker can repeat the same access.

Administrators with WP-CLI can run this read-only core integrity check from the correct WordPress installation directory:

wp core verify-checksums

The official command documentation explains that this compares core files with WordPress.org checksums without loading WordPress itself. It does not clean files or verify the database, uploads or every plugin. Investigate differences against the installed version and locale; checksum success is one limited result, not a clean-site certificate.

Review administrator roles, scheduled tasks, application credentials, configuration and rewrite rules with the host. Remove confirmed malicious additions while preserving required site behavior. Avoid bulk deletion based on filenames, modification dates or unfamiliar code alone.

Once access is under control, apply supported updates, restrict unnecessary write permissions and remove unused software. The WordPress hardening guide gives the broader maintenance framework. SiteValley’s basic WordPress security tips provide a short introduction to ongoing account and plugin hygiene.

Verify Recovery Before Reopening

AI-generated conceptual photograph of a website owner checking the same contact form on a desktop monitor and a phone.

Check both security findings and ordinary visitor tasks. Record the scope and time of the final checks so another administrator can see what was verified and what remains uncertain.

  1. Repeat internal and external scans, investigate unresolved findings and confirm that suspicious accounts or files have not returned.
  2. Test public pages in a logged-out browser on desktop and mobile. Recheck the URLs and conditions that originally showed the problem.
  3. Test login, search, forms and, for stores, checkout using the payment provider’s supported test process. Confirm notification delivery and integrations, not just the visible confirmation screen.
  4. After repairing the source, clear relevant application/CDN caches and check again for stale injected content.
  5. Keep monitoring access, error and resource logs after reopening, and take a fresh recovery backup once the repaired state is verified.

When checking forms, review their recipients, integrations and notification behavior as well as page layout. Our WordPress contact-form guide explains the features that may need retesting after a plugin replacement.

If Google still flags the site, use Search Console’s Security Issues report. Its sample URLs are examples rather than a complete list. Fix all issues in the report, document the changes and request a review when ready. Browser warnings can persist while review is pending; do not promise visitors an instant removal time.

For future recovery planning, compare backup retention, restore scope and support access. SiteValley Pro Web Hosting currently lists daily backups with 60 recovery points, Imunify360 protection and 24/7 support at $59.40 per year. Confirm the current web-hosting offer and restoration process with support. Those features help preparation; they do not guarantee incident cleanup or preservation of orders placed between backups.

Frequently Asked Questions

Can I remove WordPress malware without reinstalling everything?

Sometimes, if the affected files, records and access paths can be identified and repaired confidently. Widespread compromise or repeated reinfection may justify rebuilding from trusted packages and carefully recovered data. Preserve evidence and have the host help decide the scope before replacing the live site.

Will restoring yesterday's backup fix a hacked site?

Only if it is suitable and the original entry point is closed. The infection may predate yesterday, and a rollback may discard recent orders or submissions. Test a known-good restore point, reconcile legitimate changes and patch the cause before reopening.

Why does a scanner say the site is clean while visitors still see redirects?

The scanner may not see the affected page, visitor condition or server-side file. Cached content can also persist after repair. Compare the exact URL, device, login state and request conditions, then combine public-page checks with file, database and hosting-log investigation.

Does Wordfence repair every infected plugin file?

No. Repair depends on an available trusted original, and custom or commercial code may need a replacement from its developer. Review each finding and preserve legitimate custom work. Repairing a file does not establish that accounts, database content and other entry points are safe.

Real Clients Feedback

250+5-Star Ratings
7+YrsCollecting Reviews

SiteValley.com is rated 4.8 / 5 based on 329 Reviews »

Logo

Ready to work together towards your success?

We love taking your call.