WordPress Mobile Redirect Malware means malicious code redirects selected mobile visitors while desktop administrators may see a normal site. Treat the visible payload as evidence of a broader compromise until the entry point and persistence path are understood.
Symptoms
- Phones redirect to spam, gambling, fake update or scam pages while desktop appears normal.
- The redirect happens only on the first visit, after search/ad clicks or in certain countries.
- Unknown JavaScript or conditional PHP checks device/user agent before redirecting.
- Clearing cookies or changing network/device makes the behavior reappear.
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
- Reproduce from real mobile devices and clean sessions, recording destination/referrer conditions.
- Inspect page/network requests for conditional external scripts.
- Trace suspicious PHP/JavaScript/database code and remote loaders.
- Compare CDN/origin behavior and logged-in/logged-out responses.
Recovery
- Remove the redirect payload, loader and persistence mechanism.
- Clean affected files/database and compromised third-party integrations.
- Patch the vulnerability or credential path that allowed injection.
- Purge cache/CDN after the origin is clean.
- Retest across mobile devices, networks and search/referral entry paths.
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 Mobile Redirect 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 mobile redirect 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 Mobile Redirect Malware?
Send the site URL and exact behavior you or visitors see. Do not send passwords in the first message.
Open a security incident