WordPress Core File Malware means files inside WordPress core directories have been modified or added so malicious code runs as part of normal application execution. Treat the visible payload as evidence of a broader compromise until the entry point and persistence path are understood.
Symptoms
- Integrity checks report modified WordPress core files.
- Unknown PHP files appear inside wp-admin or wp-includes.
- Core files contain obfuscated loaders, redirects or injected includes.
- Replacing one core file helps temporarily but the modification returns.
Indicators of compromise
Indicators should be interpreted in context. Preserve enough evidence to distinguish a compromised origin from stale cache, a legitimate customization or a third-party service before deleting files.
How this threat persists
Persistence may live in a different layer from the symptom: a backdoor, scheduled task, MU plugin, database loader, compromised credential, shared-hosting account or remote script can recreate the visible malware after an incomplete cleanup.
Investigation
- Compare wp-admin/wp-includes against the exact official WordPress release, excluding expected configuration/content areas.
- Record modified timestamps and request logs for suspicious files.
- Search for persistence outside core before replacing files.
- Review account-level access, credentials and vulnerable plugins/themes that could write the modifications.
Recovery
- Replace compromised core directories with trusted files from the correct WordPress version.
- Remove backdoors/loaders outside core that can reinfect them.
- Patch the entry point and rotate privileged credentials.
- Verify database, uploads, MU plugins and cron for additional persistence.
- Re-run integrity and behavioral checks after recovery.
WP•FIX treats security incidents as root-cause investigations. Removing the visible payload is only one step; recovery also checks persistence, credentials, vulnerable components and the scope of access the attacker may have had.
Prevention after cleanup
Prevention depends on the confirmed entry point. Typical post-recovery work includes updating or replacing vulnerable components, rotating exposed credentials, removing unused privileged access, verifying clean backups, reducing unnecessary write/execute paths and monitoring the affected layer for recurrence.
FAQ
Is WordPress Core File Malware always easy to detect?
No. Conditional behavior, remote loaders, cache variants and hidden persistence can make a compromised site appear normal to administrators.
Can I remove only the visible wordpress core file malware payload?
That may stop the immediate symptom, but reinfection is likely if the loader, backdoor or original entry point remains.
Should I restore a backup?
A known-clean backup can be useful, but it should be restored only after confirming its date and addressing the entry point; otherwise the site can be reinfected.
When should I request professional incident response?
If visitors are exposed, the site is blacklisted, privileged access may be compromised, malware returns, or the infection spans multiple layers/sites, a controlled incident-response workflow is safer than repeated file deletion.
Seeing signs of WordPress Core File Malware?
Send the site URL and exact behavior you or visitors see. Do not send passwords in the first message.
Open a security incident