Blog

The FBI Says Hacked WordPress Sites Are Poisoning Google Search — Check Yours Tonight

By Juyel Rana · November 22, 2026 · Updated November 22, 2026

The FBI Says Hacked WordPress Sites Are Poisoning Google Search — Check Yours Tonight

The FBI doesn't usually put the letters "SEO" in a cyber alert. On November 16, it did.

Its FLASH alert — number CC-111626-MW — is about a piece of malware called Gootloader, and it reads like something out of an SEO horror story. As of October 2026, the FBI had found more than 1,000 infected WordPress sites and 216 domains run by the Gootloader operator. The attacks that followed are linked to over $28 million in ransomware payments.

Here's the part that should make every WordPress owner sit up: the people getting hurt weren't mostly the site owners. They were the people who clicked on the search results.

How a hacked site becomes a trap

Gootloader has been running since 2020, and the FBI's version of the chain is brutally simple.

First, the operator scans WordPress sites for xmlrpc.php — a standard endpoint that attackers love because it's handy for guessing passwords. Then it gets in with stolen or guessed logins, or through a vulnerable plugin or theme. Once inside, it injects posts, messes with XML-RPC and REST routes, and changes JavaScript files.

Then comes the SEO part. The hacked site starts publishing pages for oddly specific, low-competition searches — the FBI gives jurisdiction-specific contract clauses as an example. Hidden keyword links and arranged backlinks push those pages up the rankings until they sit right next to legitimate results.

A person searching for that exact phrase clicks, and the trap springs. Researchers at Sophos describe the lure as a fake forum thread that appears to ask the very question the victim just typed into Google. The "answer" is a download: a JavaScript file named after the search itself. Open it, and the attacker has a foothold on the machine. From there, ransomware often follows.

And the site owner? They see nothing. A traffic filter decides who gets the trap based on country, referrer, cookie, or IP address — everyone else, including the person who owns the site, gets the normal page. That's why owners usually hear about it from a customer, or from a Google warning, instead of spotting it themselves.

Your site is a target even if you're not a law firm

Gootloader's lure pages mostly targeted lawyers — people searching for agreements, clauses, and legal templates. But the site it lived on could be about anything. The FBI's keyword list also includes zoning, tax, drinking-age laws, and even SQL commands. The topic of the lure had nothing to do with the site hosting it. The operator just needed any WordPress site it could break into.

So if your site gets used, you pay three ways. Your visitors get hurt, and it was your domain they trusted when they clicked. Google can flag the site as hacked, show warnings, or hit it with a manual action — and a pile of hidden links and off-topic pages drags down how search engines see the whole site. And your host can suspend the account for serving malware. On shared hosting, one infected site can put its neighbours at risk too.

Days before the alert, the Justice Department said it had removed Gootloader from more than 100 servers in an action tied to Operation Endgame. That sounds like a win, and it is — but the FBI's alert also lists other campaigns doing the same trick with WordPress, so this isn't a one-off problem with a single fix.

The 15-minute check in Search Console

The FBI names Search Console directly as an early-warning tool, and it's the fastest place to look. Set aside fifteen minutes tonight.

Start with the Performance report. Sort by queries and look for anything that has nothing to do with your business — legal terms, contract phrases, random product names. If your plumbing site is suddenly getting impressions for a Delaware operating agreement, that's not a win. It's a warning.

Then check the Pages report for a sudden jump in indexed pages you never published, often with dated-looking URLs. Then the Security issues report and Manual actions — if Google has spotted something, it'll say so here.

A couple of quick checks outside Search Console help too. Search Google for site:yourdomain.com plus a word like "agreement" or "definition" and see if pages you don't recognise show up. And look at your own site the way a stranger would: a private browser window, on your phone, on mobile data, logged out. These scripts hide from logged-in admins and known IP addresses, so the view from your office desk is the least reliable one.

Inside WordPress, look for admin users you don't recognise — especially ones with random-looking names — files in wp-content/mu-plugins you didn't add, PHP files sitting in wp-content/uploads where they don't belong, and recent changes to theme JavaScript, .htaccess, or index files. If you can read your access logs, a flood of POST requests to xmlrpc.php is another red flag.

One odd query or one strange file proves nothing on its own. Two or three of these together, and you should treat it as serious.

If you find something, don't just restore a backup

The FBI gives a clear order of work, and restoring a backup is not step one. It goes like this:

Contain it first — put the site in maintenance mode or restrict public access, but keep a copy of the files, database, logs, and hosting settings for investigation. Then reset every credential from a clean device: hosting panel, SSH, SFTP, WordPress admins, database, API keys, CDN — and revoke active sessions and application passwords. Then figure out how they got in: a weak password, an old plugin, an exposed XML-RPC endpoint. Close that hole first, and only then restore from a backup you know is clean.

After that, clean up search: remove the spam pages, ask Google to remove the injected URLs in Search Console, and request a review if you got a manual action. And report it — the FBI asks for suspected Gootloader intrusions to go to a local FBI field office or the Internet Crime Complaint Center at ic3.gov.

The blunt part: restoring a backup without fixing the entry point just invites the attacker back. Some of these infections reinfect on every page load if any piece is left behind.

Lock it down before it happens

Most of the FBI's WordPress protections are things any site owner can do this week. Turn on automatic updates for core, plugins, and themes. Delete what you don't use — unused plugins, themes, old user accounts, forgotten staging sites. Every one of them is a door. Use strong multi-factor login for your WordPress admins and your hosting account, because a stolen password is how Gootloader got in. And if you don't need XML-RPC, turn it off. Most modern sites don't.

A few items sit with your host or developer: running PHP as a low-privilege user, blocking PHP from executing inside wp-content/uploads, keeping sites on the same account isolated from each other, a web application firewall, and file-integrity checks that flag unexpected changes to core files, plugins, themes, or JavaScript. Worth asking your host what it actually does on that list — on cheap or unmanaged setups, the honest answer is sometimes "nobody."

If you manage sites for clients, add a monthly security line to your reports: plugins updated, admin users reviewed, Search Console checked. Ten minutes per site, and it's the check that catches a Gootloader-style infection before a client hears about it from a stranger.

Sources

Keep reading on heyjuyel.com

Run a WordPress site for your business — or for clients? A hacked site doesn't just hurt your rankings; it can hurt your visitors. If you'd like a second pair of eyes on your site's SEO and security basics, get a free SEO audit and I'll take a look.