The FBI's November 16 flash alert ties Gootloader, malware spread through poisoned Google search results, to more than 1,000 hacked WordPress sites, 216 controlled domains, and over $28 million in ransomware payments going back to 2020. If you run WordPress, or hired someone who still does, this is five minutes well spent this week. If you don't run WordPress at all, most of this won't touch you.
What did the FBI's Gootloader alert actually say?#
The alert (reference CC-111626-MW) describes an operation running since 2020: buy up long-tail, low-competition search phrases (an obscure legal clause, a state-specific regulation), then get a fake "document" result ranking for them, hosted on a hacked WordPress site. Someone searches, clicks, downloads what looks like the file they needed, and runs a JavaScript loader instead.
At WebEpex, we checked every client site we're responsible for against this alert's indicators the day it went out, since none of them run WordPress but a few sit behind shared hosting with similarly old defaults.
WordPress sites get in mostly through xmlrpc.php, the old XML-RPC endpoint most hosts still leave switched on, which attackers use to brute-force admin logins. Once in, the operator doesn't deface anything. They quietly add hidden posts and links that mainly search engines see, turning someone else's domain into part of their own ranking infrastructure. Gootloader is a precursor, not the ransomware payload itself. That's the FBI's own framing, not mine.
Does this actually affect your business?#
If your site runs on WordPress and nobody's rotated admin credentials recently, checked which plugins are still active, or touched xmlrpc.php, this is relevant to you today. The FBI's 1,000+ figure is "as of October," so more sites have likely joined since this alert went out.
If you're not on WordPress (Shopify, Webflow, a custom build), this campaign isn't built to reach you. It leans on WordPress's plugin ecosystem and one legacy endpoint. Worth remembering anyway: SEO poisoning as a technique doesn't care what you're built on. Only Gootloader's delivery method does.
One flag. Recent targeting skews toward US legal and professional-services sites, even though the full 1,000+ figure spans "a wide variety of sectors," per the FBI. Law firm, accounting practice, anyone publishing dense regulatory content on WordPress: move this up your list.
What's the actual trade-off here?#
The tension here cuts against WordPress's biggest strength. It's open and cheap to extend precisely because anyone can ship a plugin for it, which is also why it carries more attack surface than almost anything else running a meaningful share of the web. Not a knock on WordPress core, though. Most of these infections trace back to stolen credentials and unpatched plugins, not a flaw in the software itself.
Honest gap: the alert doesn't say how many sites are still infected, or name which ransomware groups eventually got paid once Gootloader opened the door. I'm reading "precursor to ransomware" and filling in the rest with reasonable inference, not a documented chain. Worth saying plainly instead of pretending otherwise.
The fix isn't free, either. Disabling xmlrpc.php can break some mobile publishing apps and older plugin integrations. Weigh that before flipping the switch everywhere.
How we're handling it at WebEpex#
At WebEpex we don't build client sites on WordPress. Our stack is Next.js, PostgreSQL and Node.js on self-hosted VPS infrastructure behind PM2 and Nginx, so this alert doesn't touch anything we've shipped. Not us dodging the question. We built it this way for self-hosted security reasons years before this alert existed, on the theory that fewer moving parts someone else wrote means less of exactly this kind of attack surface.
Where it does touch us: prospects occasionally come to us wanting an existing WordPress site rebuilt. We added a short check to that intake audit the week this alert went out, covering xmlrpc.php exposure, plugin count, and last credential rotation, so a migration doesn't start by quietly inheriting someone else's compromise. It now sits next to the security checks we already run before touching a self-hosted stack.
For sites we didn't build but get asked to look at, Search Console is usually the first place this shows up: pages you didn't write, ranking for queries you never targeted.
What I'd tell a client this week#
If someone asked me this week, here's the list, in order:
- Check whether xmlrpc.php is still open (most hosts leave it on; Jetpack and some mobile apps use it, which is exactly why it rarely gets closed)
- Disable it, or lock it to known IPs, if you don't need it
- Rotate admin, hosting and database credentials from a clean machine, not the one you're worried about
- Spend ten minutes in Search Console looking for indexed pages you don't recognize
Found something in that last step? That's not a watch-and-wait situation. Get someone who does WordPress security properly on it today, not next sprint.
If you're not sure whether your own setup is exposed, send me what you're running and I'll tell you straight, no pitch attached. cal.com/webepex/growth-review