Unexpected WordPress File Changes: How to Triage Integrity Alerts
Integrity alerts can be updates, deployments, custom edits or compromise. Classify source, scope and timing before restoring files.
WORDPRESS RESCUE JOURNAL
Specialist-reviewed guides for broken, compromised or blocked websites. Diagnosis, security and practical decisions without blind recipes.
START WITH THE VISIBLE SYMPTOM
These guides help you preserve evidence, avoid risky shortcuts and decide when the problem needs a controlled technical intervention.
Understand the fatal error behind the generic message and the evidence worth preserving before changing plugins or themes.
Open the guide 02Learn why a blank page should be diagnosed through protected logs instead of exposing debug information publicly.
Open the guide 03See where conditional redirects hide and why clearing one server rule may not remove the infection.
Open the guide 04Separate a legitimate access problem from signs of compromise and recover control without leaving a bypass.
Open the guide 05Compare rollback, compatibility repair and safe update routes when production fails after a release.
Open the guide 06Trace the sales journey from browser and session through payment callback, order creation and stock.
Open the guideIntegrity alerts can be updates, deployments, custom edits or compromise. Classify source, scope and timing before restoring files.
Attackers can store scripts, redirects or encoded configuration in wp_options. Identify the consumer before deleting data.
Must-use plugins load automatically and cannot be deactivated normally. Audit the directory and any loader files directly.
Attackers use WP-Cron to restore files, users or remote payloads. Record hooks and callbacks before deleting them.
Fake update pages are injected social-engineering payloads, often conditional by device or referrer. Reproduce safely and trace the loader.
A hosting suspension is containment by the provider. Preserve the account, obtain the evidence and clean every affected site before requesting reactivation.
Outbound spam can come from compromised code, abused forms, stolen SMTP credentials or hosting-level scripts. Contain sending before cleanup.
If index.php changes again after replacement, another process still has write access and persistence. Track the writer, not the victim file.
Repeated .htaccess changes can be legitimate rewrites or active persistence. Diff each version and identify the writer.
WP-VCD infections often arrive through nulled themes or plugins and inject code across active themes. Replace the source and remove persistence.
PHP inside uploads is a strong compromise signal on most sites. Preserve, block execution, identify the uploader and remove persistence.
Spam URLs absent from wp-admin are usually generated by files, rewrites or database options. Inspect the live response and routing path.