WordPress Cryptominer Malware means compromised WordPress or hosting resources are used to run mining code in visitors’ browsers or on the server without authorization. Treat the visible payload as evidence of a broader compromise until the entry point and persistence path are understood.
Symptoms
- Unexpected high CPU/load occurs even when traffic is normal.
- Pages load unknown JavaScript/WebAssembly related to mining or worker scripts.
- Unknown long-running processes appear under the hosting account where process visibility is available.
- Performance degrades and hosting providers report abusive resource consumption.
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
- Separate browser-side script injection from server-side process/resource abuse.
- Inspect page source/network requests and server process/resource history.
- Review cron, startup hooks, writable directories and suspicious binaries/scripts.
- Trace the original vulnerable component or credential compromise.
Recovery
- Remove injected mining scripts and any server-side miner/persistence.
- Restore trusted files and clean affected database content.
- Patch the entry point and rotate credentials.
- Review neighboring sites/account scope where resources are shared.
- Monitor CPU, process and outbound network behavior 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 Cryptominer 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 cryptominer 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 Cryptominer Malware?
Send the site URL and exact behavior you or visitors see. Do not send passwords in the first message.
Open a security incident