WordPress Login Credential Stealer means malicious code captures or forwards credentials entered into wp-login.php or a fake login interface. Treat the visible payload as evidence of a broader compromise until the entry point and persistence path are understood.
Symptoms
- wp-login.php loads unknown external scripts or makes unexpected network requests.
- Administrators are redirected to a fake login/verification page.
- Credentials are compromised even after passwords were recently changed.
- Theme/plugin/core files contain code that hooks login handling or injects browser scripts.
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
- Inspect login-page source/network activity from a clean browser.
- Compare wp-login.php and core files with trusted WordPress sources.
- Review hooks/plugins/MU plugins that run on login/admin pages.
- Assume credentials entered during the compromise may be exposed and inspect access logs for subsequent use.
Recovery
- Remove the credential-stealing code and all persistence.
- Restore trusted login/core files and compromised components.
- Rotate administrator, hosting, SFTP/SSH and related credentials from a clean device as appropriate.
- Invalidate sessions/application passwords and review unknown users.
- Patch the entry point and monitor privileged logins 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 Login Credential Stealer 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 login credential stealer 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 Login Credential Stealer?
Send the site URL and exact behavior you or visitors see. Do not send passwords in the first message.
Open a security incident