What Online Game Account Raids Teach About WordPress Logins
Last March a bakery owner sent me a screenshot of her WordPress security plugin log: 14,212 failed login attempts in nine days, all aimed at a username called "admin". She did not have a user called "admin", so none of them worked.

Last March a bakery owner sent me a screenshot of her WordPress security plugin log: 14,212 failed login attempts in nine days, all aimed at a username called "admin". She did not have a user called "admin", so none of them worked. But one of the attempts later in the week used her real username, the one shown in her author archive, and the password guesses started looking a lot like passwords she had used on other sites. That is the moment a nuisance becomes a real threat.
Anyone who has played a popular online game for a few years has seen this exact script from the other side. Steam, Riot and Epic accounts get raided constantly, and almost never because someone "hacked" the game. Attackers take email and password pairs leaked from some unrelated site and try them everywhere. Gamers learned the defences the hard way, after losing skins, ranked accounts and years of progress. Small business owners can borrow those lessons for free.
How a game account raid actually happens
The method has a name, credential stuffing, and it is boring rather than clever. A forum, a shopping site or a mobile app leaks its user table. The list ends up for sale, sometimes for less than ten dollars per million rows. Automated tools then try each pair against game launchers, email providers and, yes, any WordPress login page they can find at /wp-login.php.
Game companies saw this early because their accounts carry value that can be resold within minutes. A rare item on a Counter-Strike account can be traded off before the owner wakes up. That is why Valve pushed the Steam Guard mobile authenticator and added trade holds of up to fifteen days when a trade is made without it. The hold looks annoying, and it is, but it turns a fast theft into a slow one that the owner can notice and stop.
A WordPress site does not have skins to steal, but it has something attackers value more: a trusted domain. A compromised small business site gets used to host phishing pages, inject spam links into old posts, or redirect mobile visitors to scam pages. In the cleanups I do, the owner usually discovers it weeks later when Google shows a warning in search results or the hosting company suspends the account.
What gamers changed, and the WordPress equivalent
Players who got burned tend to make the same handful of changes. Each one has a direct counterpart on a WordPress site, and none of them costs money.
| What players did after a raid | WordPress equivalent | Time to set up |
|---|---|---|
| Turned on an authenticator app (Steam Guard, Riot 2FA) | Two factor login with an app such as Google Authenticator, via a plugin like WP 2FA or Wordfence | About 10 minutes |
| Stopped reusing the password from their old forum account | A unique password from a password manager for every admin user | 5 minutes per user |
| Hid their account email from public profiles | Stop showing the login username as the public author name | 2 minutes |
| Checked active sessions and logged out unknown devices | Review Users and log out other sessions; remove old admin accounts | 15 minutes |
| Accepted trade holds and login alerts | Limit login attempts and get an email when a new admin logs in | 10 minutes |
The username point surprises people. WordPress shows author archives at an address built from the login name unless you set a separate display name. Attackers scrape it. Go to Users, open your profile, set a nickname, and choose it under "Display name publicly as". The login name stays private.
Where I disagree with the usual advice: renaming the login page
Many guides tell owners to move /wp-login.php to a secret address and call it a security fix. I see why. The failed-login log goes quiet overnight, and that feels like progress. Gamers have a version of this too: players who change their in-game name after a raid and assume they are safe, while still using the leaked password.
Hiding the door does not lock it. Renamed login pages still leak through XML-RPC, through REST API endpoints, and through plugins that print the login link. I have cleaned up three sites in the past year that had a renamed login page and were still breached, because the owner reused a password that had leaked from a different service. In all three, two factor authentication would have stopped the attacker at the second step.
Renaming is fine as a noise reducer if your log is flooding your inbox. It is not a defence by itself, and I would rather an owner spend those ten minutes turning on two factor login than installing a renaming plugin.
A raid on a real site, step by step
The bakery case went like this. After the attempts using her real username, I checked Have I Been Pwned for her email address. It appeared in four breaches, including a 2019 leak from a recipe site where she had used a variation of the same password she used for WordPress. The attacker's list probably contained that variation.
We changed her password to a 20-character random one stored in Bitwarden, switched on app-based two factor login for both admin users, set her public display name to "The Bakery Team", and disabled XML-RPC because nothing on the site used it. We also removed a third admin account belonging to a designer who had built the site in 2021 and had not logged in since. Total time, about forty minutes with tea.
The failed attempts did not stop. They never do. But the log now shows them failing at the two factor step, which is exactly what a Steam user sees when someone tries their leaked password: an alert, a failed attempt, and nothing lost.
If something has already gone wrong and you suspect a break-in, start with the backups before you touch anything else. My notes on keeping offsite backups you can actually restore explain why the copy on the same server cannot be trusted after a hack. More guides sit under security and backups.
One job for this week
Open Users in your WordPress dashboard and count the administrators. In most small business sites I review, there are between three and six, and only one or two are still in use. Downgrade or delete the rest, then turn on two factor login for whoever remains. That one pass closes more doors than any firewall setting I can recommend, and you will finish it before lunch.
FAQ
Is two factor authentication enough to stop WordPress login attacks?
It stops nearly all password-based attacks, including credential stuffing. It does not protect against a vulnerable plugin, so updates still matter.
Which two factor method should a small business use?
An authenticator app is the sensible default. SMS codes are better than nothing, but SIM swap attacks make them weaker, a lesson many gamers learned when their phone number was hijacked.
Should I limit login attempts on WordPress?
Yes. Most security plugins can lock an address out after five or so failures. It cuts noise and slows automated tools.
How do I know if my password has leaked?
Check your email on Have I Been Pwned. If it appears in a breach and you reused that password anywhere, change it everywhere, starting with your site and your email account.
More in Games
Games
What Online Game Health Bars Teach About Uptime Monitoring
In Valheim, when your character gets hungry, cold or wet, small icons appear in the corner of the screen long before your...
Games
What Budget Phone Gamers Teach Shops About Lightweight Sites
Walk past any tea stall in Dhaka in the evening and you will see someone playing Free Fire or PUBG Mobile on a phone that cost...
Games
How Lost Online Gaming Usernames Explain Domain Expiry Risks
My nephew lost his Xbox gamertag last year. He had used the same short name since he was eleven, stopped playing for a couple...