Surfaces our work more for you across Google Search and AI answers.
Your website loads. Your homepage looks like your homepage. Your contact form still sends. And somewhere in Google's index, your domain is also the top result for "zoning government definition," serving a fake legal forum to strangers who will never see your business name. You'd be the last to find out, because the page is built to hide from you.
Quick read: On November 16, 2026, the Federal Bureau of Investigation (FBI) published FLASH alert CC-111626-MW on Gootloader, malware that uses "a JavaScript malware loader, compromised websites, and search engine optimization (SEO) techniques" to break into organizations. As of October 2026 the FBI had identified "over 1000 infected WordPress sites and 216 domains controlled by the Gootloader administrator, which led to over $28 million in ransomware payments" (FBI FLASH, PDF; reported by Search Engine Roundtable on November 17). The compromised sites "acted as lure pages, redirectors, traffic filters, or relay infrastructure," ranking for low-competition phrases such as "a jurisdiction-specific contract clause" and showing a fake download page only to selected visitors. The way in was WordPress housekeeping: stolen credentials, "vulnerable plugins and themes," and the
xmlrpc.phplogin endpoint. A related Justice Department operation announced November 12 removed the malware from more than 100 servers, including compromised WordPress sites. The FBI's own mitigation list tells site operators to review Search Console for "unrelated legal or business queries, sudden indexed pages, manual actions, and security warnings."
How a plumber's website ends up answering legal questions
Gootloader is a business. The people running it want employees at law firms to download a file, open it, and hand over a foothold that gets sold on to ransomware crews. To do that they need web pages that rank in Google for the exact phrases a paralegal types at 4 p.m. on a Thursday. Building those pages on their own domains would get them flagged. Building them on yours works better, because your domain has years of legitimate history and nobody is watching it.
So the FBI describes a pipeline. First, scan the open web for WordPress installs with the xmlrpc.php endpoint exposed, an old remote-publishing interface that happily accepts thousands of password guesses. Second, get in with stolen credentials or through a plugin or theme with a known hole. Third, plant the goods: injected posts, hidden keyword links, modified JavaScript, new routes in the site's own application interface. The FBI's example of what gets injected is a list of links with anchor text like "Zoning Government Definition" and "Which Parent Will Get the Child Tax Credit," tucked inside an element no visitor will ever see.
The part that makes this hard to catch is the filter. Gootloader runs what the FBI calls a traffic distribution system that sorts visitors "by country, referrer, cookie, or IP address," IP being the Internet Protocol address that identifies a connection. Sophos, whose researchers traced the operation's control server back to 2018, found the fake page appears only for someone who clicked a Google result, is in a targeted country, and is on a Windows browser; on that first visit the script "deletes the original content" of the page and "replaces it with the fake forum text," then adds the visitor's address to a blocklist so a second look shows nothing (Sophos). Everyone else, including you, your web designer, and whoever you ask to take a look, gets the ordinary page. Sophos's blunt summary of the hidden links: "None of these links will appear when you browse to the page, but search engines index them."
Google, meanwhile, sees the version built for Google.
Why a small business is the target
The FBI says Gootloader's search terms were aimed at attorneys, in-house counsel, and legal operations staff. You are not that target. Your website is the venue, the way a vacant storefront gets used for a card game. Nobody picked your business; they picked your unpatched plugin.
And the plugin layer is where the holes are. Patchstack's State of WordPress Security report counted 11,334 new vulnerabilities across the WordPress ecosystem in 2025, a 42% increase on 2024. Of those, 91% were in plugins and 9% in themes, with six in WordPress core itself. The weighted median time from disclosure to first exploit attempt was five hours (Patchstack). An update that waits for "when I get a minute" loses that race by a month.
Here's the thing about the damage. The ransomware happens to someone else's network. The bill your business pays is what happens to your domain while it hosts the lure:
- Google warns searchers before they reach you. Search Console's Security Issues report defines hacked content as "any content placed on your site without your permission because of security vulnerabilities in your site," sorted into code injection, content injection, and URL injection, and warns that affected pages or sites can carry a warning label in search results or a full-screen interstitial in the browser (Search Console Help). A customer who searches your business name and gets a red screen does not read the fine print.
- Your index fills with junk. Pages of legal questions now sit under your domain next to your six real service pages. Google's picture of what your site is about blurs accordingly.
- The crawler's copy is the record. Whatever Googlebot fetched is what Google and the AI answer engines work from. What the crawlers record is what the answer engines repeat, and a site that reads as half plumbing, half divorce law is not a site any of them will quote on plumbing.
- Your host may act before you do. Many hosts suspend accounts that serve malware, and the suspension page they put up is theirs, not yours.
I ran a grooming salon for years, and the problems that cost the most were never the loud ones. A dryer that quits announces itself. A drain that backs up a little every week doesn't, until it does. A hacked site is the drain.
Six checks that take an afternoon
None of this needs a security background. It needs Search Console access, your WordPress login, and a willingness to read lists.
Search your own site. In Google, type
site:yourdomain.comand page through the results. Google's own hacked-site guidance says this "shows you all the pages on your site, including pages a hacker might have added" (Google, web.dev). You are looking for titles you didn't write, in topics you don't cover, in languages you don't speak. Do the same search in Bing as a cross-check, not a substitute: Sophos found the poisoned results "don't typically appear in other search engines' results pages."Open Search Console and read three reports. Security Issues first; a green check mark is the answer you want. Then Pages (indexing), looking for a sudden jump in indexed addresses, the Uniform Resource Locators (URLs), that you can't account for. Then Performance, sorted by query, looking for the "unrelated legal or business queries" the FBI tells operators to watch for. A small site's branded and non-branded queries are easy to tell apart; a plumbing company earning impressions for "sports betting legal in Virginia" is the tell.
Look at your pages the way Google does. Because of the visitor filter, your browser is the worst tool for this. Search Console's URL Inspection tool shows the page as Googlebot fetched it, and Google's hacked-site guidance points to it for this check. Inspect your homepage and two or three top pages, then view the crawled Hypertext Markup Language (HTML) and search it for words that have no business there: "agreement," "attorney," "law," "definition."
Read your WordPress Users list. Every account should belong to a person you can name. The FBI's table of related WordPress campaigns describes one operation, DollyWay, that persists through "hidden admin users with random hex names." A user called
a3f9c2e1with Administrator rights is not a plugin's doing.Read the Plugins and Themes lists, including the ones you can't see. Count the active plugins and know what each one does. Delete the inactive ones; inactive is not the same as harmless. Then have whoever manages your hosting check the
wp-content/mu-pluginsfolder, which WordPress loads automatically and never shows in the admin plugin list. Two of the campaigns in the FBI's table hide there.Close the login side door. Ask your host or developer whether
xmlrpc.phpis disabled. The FBI's recommendation is to turn it off if unused and, if some integration needs it, to rate-limit it and allow only the methods that integration uses. While you're there: multi-factor authentication on every administrator account, and automatic updates on core and on plugins you trust.
If any of the first three turns something up, the FBI's immediate-response list is the one to follow: put the site in a controlled maintenance state while keeping a forensic copy of the files, database, and logs; reset every credential from a clean computer, meaning the hosting panel, the server logins (Secure Shell, or SSH, and Secure File Transfer Protocol, or SFTP), the WordPress admin, the database, any application programming interface (API) keys, and the content delivery network (CDN); revoke active sessions and application passwords; and "restore from a known-clean backup only after removing the vulnerability or stolen credential that allowed entry." That maintenance state should answer with a 503, for the reasons in the holding page that tells Google everything is fine.
Cleanups that leave the door open
- Deleting the pages and calling it done. The pages are the symptom. The stolen password or vulnerable plugin that created them is still there, and these operations are built to come back; the FBI describes DollyWay as one that "reinfects on every page load." Google's guidance on cloaked-keyword hacks puts it this way: "Hackers try to trick you into thinking the page is gone or fixed when it's still hacked."
- Restoring last week's backup. If the break-in was three months ago, last week's backup contains it. Restore from before the entry, after the hole is closed, or you've restored the burglar along with the furniture.
- Checking from your own laptop and declaring it clean. You are the one visitor the page is designed to hide from. Use URL Inspection or nothing.
- Trusting a green uptime monitor. The site was up the whole time. That was the point.
- Changing passwords from the computer you suspect. The FBI's instruction is to reset credentials "from a clean system," because a compromised machine hands the new password straight back.
- Installing a security plugin and considering the matter closed. A scanner that runs is good. A scanner nobody reads is a plugin that needs updating.
- Requesting a Google review before the fix is complete. Search Console's review process asks you to describe what you fixed and warns that repeat requests while one is pending make the wait longer. Fix first, then ask once.
Your host will patch the server and keep the lights on. Your host does not patch your plugins or read your Search Console; that work has an owner or it has nobody. A monthly pass through the six checks above is the minimum, and the first pass is the one that tells you whether the last eighteen months were as quiet as they looked.
FAQ
What is SEO poisoning?
SEO poisoning is getting malicious or deceptive pages to rank in search results so that people searching in good faith land on them. In the Gootloader case the FBI describes, the pages were planted on hacked WordPress sites, targeted low-competition legal phrases, and showed a fake forum with a download link only to visitors arriving from Google in certain countries. Everyone else saw the normal site.
How do I know if my WordPress site has been hacked?
Start with a site:yourdomain.com search in Google and look for pages you didn't create. Then open Search Console and check the Security Issues report, the Pages report for a jump in indexed URLs, and the Performance report for queries unrelated to your business. Use URL Inspection to see the page as Googlebot sees it, because hacked content is often hidden from ordinary visitors. Finally, review the Users and Plugins lists in WordPress for anything you can't name.
Why can't I see the spam pages when I visit my own site?
Gootloader and similar operations filter visitors by referrer, country, device, cookie, and IP address, and serve the fake content only to targets who match. Site owners, developers, and repeat visitors are shown the ordinary page. Search Console's URL Inspection tool fetches the page as Google does and shows the crawled HTML, which is the reliable way to see what the crawler saw.
Does a hacked site hurt my Google rankings?
It can hurt in several ways. Google's Security Issues report can mark the site with a warning in search results or a browser interstitial. Hundreds of unrelated pages indexed under your domain dilute what the site is about. The pages Google and AI answer engines have on file are the ones they draw on, so a site that reads as spam is not one they quote. Hosts may also suspend an account that serves malware.
What is xmlrpc.php and should I disable it?
It is an older WordPress interface for remote publishing that the FBI says Gootloader's operator scanned for, because it accepts login attempts in bulk and is a common target for password guessing. The FBI recommends disabling it if nothing uses it and, if an integration requires it, rate-limiting it and allowing only the methods that integration needs. Most small-business sites have nothing that uses it.
My site was hacked. What do I do first?
Follow the FBI's order of operations: put the site in a controlled maintenance state (served with a 503) while preserving a copy of the files, database, and logs; reset every credential (hosting panel, SSH and SFTP logins, WordPress admin, database, API keys, CDN) from a clean computer; revoke active sessions and application passwords; find the way in; then restore from a backup taken before the compromise, only after the vulnerability or stolen credential has been removed. Request a Google review once, after the fix.
Under ongoing Care, reading Search Console for pages and queries that shouldn't exist is a line on the monthly runbook, next to the plugin and credential checks nobody enjoys and nobody skips.
Want a back office for your site?
The build is free on any Care plan with a 12-month minimum. Care starts at $199/mo, and you can switch tiers anytime.
Apply for a build slot →RELATED READS