The FBI Says Hacked WordPress Sites Fuel Ransomware (2026)

On November 16, 2026, the FBI published an alert that does something unusual: it puts search engine optimization inside a ransomware warning. Criminals broke into more than 1,000 WordPress sites, used them to rank bait pages in Google, and the FBI links the operation to over $28 million in ransom payments. Here is what the alert says, what it does not, and what a small business with a WordPress site should check.

A limestone county courthouse with a clock tower on a foggy blue pre-dawn morning, bare trees, a wet empty street and one storefront with a single warm light on in its window

Short answer: The FBI says a malware operation called Gootloader used SEO techniques and compromised WordPress sites to infect organizations, and that as of October 2026 it had identified over 1,000 infected WordPress sites, 216 domains run by the operation's administrator and over $28 million in ransomware payments tied to the activity. The hacked sites worked as lure pages, redirectors, traffic filters or relay infrastructure. If you run a WordPress site, the alert is a reason to check who can log in, what is installed and what Google thinks your site is about. The catch is that the FBI describes a campaign aimed mostly at legal professionals, so we are applying its lessons to other trades by analogy, not by evidence.

This post is for owners of plumbing, HVAC, lawn care, dental, restaurant and retail businesses in Fort Wayne, Auburn and across Allen and DeKalb counties who have a WordPress site that someone built a few years ago and nobody has looked at since. We are not a security firm and this is not an incident response guide. It is a plain reading of a federal alert, with a checklist we think is proportionate.

A note on sources. We read the FBI alert itself, the Search Engine Roundtable report on it, a detailed write-up by Relevant Audience, Google's spam policies and the WordPress project's hardening guide. We did not test any site for this infection, we have no client case to report, and we sell website maintenance and security services, so weigh our advice with that in mind.

Key Takeaways

  • The FBI's FLASH CC-111626-MW, dated November 16, 2026, says Gootloader combines a JavaScript malware loader, compromised websites and SEO techniques to infect organizations, as a precursor to ransomware.
  • As of October 2026 the FBI identified over 1,000 infected WordPress sites, 216 domains controlled by the administrator and over $28 million in ransomware payments tied to the activity.
  • The FBI says the operation scanned for the XML-RPC file, used compromised credentials, and used stolen credentials to reach vulnerable plugins and themes. Those are ordinary weaknesses on a neglected small business site.
  • A traffic distribution system filtered who saw the bait by country, referrer, cookie or IP address, so the site owner may see nothing wrong.
  • The FBI names Search Console as a detection tool: look for unrelated queries, sudden indexed pages, manual actions and security warnings.

What Did the FBI Actually Say?

The document is an FBI FLASH, a technical alert that the bureau publishes through its Internet Crime Complaint Center at ic3.gov. This one is numbered CC-111626-MW and carries the date November 16, 2026. Its opening paragraph is short and worth reading in full, because it contains every headline number. The FBI wrote:

Gootloader is an initial access framework that uses a JavaScript malware loader, compromised websites, and search engine optimization (SEO) techniques to infect organizations.

It adds that cyber actors used Gootloader as a ransomware precursor to attack victims across a wide variety of sectors, and that, as of October 2026, the FBI identified “over 1000 infected WordPress sites and 216 domains controlled by the Gootloader administrator, which led to over $28 million in ransomware payments.” The FBI encourages organizations that have been compromised to contact it and to apply the recommendations in the document.

Search Engine Roundtable, which reported on the alert, passed along a remark from SEO consultant Bill Hartzer that is hard to improve on:

It is not often the FBI writes the letters SEO into a cyber alert.

Search Engine Roundtable also made a fair point in its own words: the technique is not new, and most people in the field have run across it before. The FBI timeline agrees. It dates this activity from 2020 and describes four years of change in tactics, from ZIP files that delivered JavaScript in 2020 and 2021, to trojanized JavaScript libraries and scheduled tasks in 2022 through 2024, to abuse of WordPress comment paths and traffic distribution services in 2025 and 2026. What is new is a federal agency putting numbers on it and telling website owners that they are part of the picture.

An isometric illustration on a navy background: a cream search bar block with an amber magnifying glass, a dotted amber path to a teal storefront house with a cracked wall and a hidden hatch on its roof, and a second dotted path to a gray office building topped with an orange warning triangle

The picture above is our simplified version of the chain the FBI describes. Someone searches. A hacked, otherwise ordinary website is in the results. The visitor who was chosen for the trap is sent onward, and the organization they work for is the one that ends up with a problem. The small business website in the middle did nothing wrong in the visitor's eyes. It was simply the delivery route.

How Does SEO Poisoning Turn a Hacked Site Into Bait?

The FBI explains that between 2020 and 2026 the operation worked from “selected search phrases with low-ranking competition.” A footnote in the alert describes these as phrases with low search volume, which lets very specific keywords be targeted. The example it gives is a jurisdiction-specific contract clause. The FBI says that, using SEO, pages controlled by the threat actors “would appear next to legitimate resources” in search results.

Two details matter here. First, the phrases were obscure on purpose. When almost nobody competes for a search, a low quality page can reach the top of the results with very little effort. This is the same logic a legitimate local business uses when it writes a page for a narrow service in a specific town. The attackers just pointed it at a different goal. Second, the FBI says hidden keyword links and arranged backlinks were used to raise the visibility of the lure pages. That is the old playbook of hiding links inside a page where visitors will not see them but search engines will.

Google already has a name for this. Its spam policies define hacked content as content placed on a site without permission because of a security weakness, and they list four examples: code injection, page injection, content injection and redirects. Page injection is the one most relevant to a small business. In Google's words, hackers sometimes add new pages to your site that contain spammy or malicious content, and “your existing pages might not show signs of hacking, but these newly-created pages could harm your site's visitors or your site's performance in search results.”

That sentence is why we think the FBI alert belongs on a marketing blog. A hacked site is a security problem and a search problem at the same time. The pages that the attackers want ranked sit on your domain. Your domain earns the trust that makes them rank.

Does This Only Hit Law Firms?

The reader's first reaction is probably relief, so we want to be careful. The alert says the search terms in this campaign were aimed at practicing attorneys, in-house counsel, law firm partners, litigation and privacy teams, legal operations professionals, general counsel and legal technology decision makers. Its timeline describes the 2025 and 2026 focus as U.S. legal professionals and legal technology decision makers. It does not list any dental practice, contractor, restaurant or retailer as a victim, and it does not enumerate the sectors it means by “a wide variety.”

Two things keep us from treating that as an all-clear. The first is the site side. The FBI says more than 1,000 WordPress sites were infected, and it does not say they were law firm websites. A WordPress site is a WordPress site. The attackers needed servers to host lure pages, and a plumbing company's forgotten WordPress install works as well as anyone's.

The second is that the alert is not limited to one gang. Relevant Audience, which summarized the alert in detail, lists the other WordPress abuse campaigns the FLASH includes. By its reading, the FBI describes an operation called DollyWay that has affected more than 20,000 sites since 2016 and uses fake plugins and hidden administrator accounts with random hex names, and another called DoubleDonut that touched more than 250 sites in 12 countries and skips visitors carrying admin cookies. It also describes the June 2026 Operation Endgame takedown, which it says cleaned 14,971 WordPress sites. We read those figures through Relevant Audience and did not check each one against the PDF line by line, so treat them as that publication's reading of the alert.

Our own analysis, which the FBI does not make, is that a small business is exposed in two separate ways. Its website can be used as bait for somebody else's staff. And its own staff can click a poisoned result when they go looking for a form, a template or a software download. We come back to the second one below.

How Did the Attackers Get Into the Sites?

The FBI's account of the break-ins is short, and it is the part a site owner can act on. It says the Gootloader administrator scanned WordPress sites looking for the XML-RPC file, xmlrpc.php, and later used compromised credentials to breach systems. A footnote describes XML-RPC as a standard WordPress API endpoint frequently targeted by attackers for brute-forcing credentials. The alert also says the administrator used stolen credentials to access vulnerable plugins and themes, and that attackers injected posts, XML-RPC and REST routes, and modified JavaScript.

In everyday terms, the list of weak points is:

  • Passwords that can be guessed or have already leaked. The WordPress project's hardening guide says that a hacker who gains access to an administrator account can install malicious scripts that may compromise your entire server, and recommends a strong password plus two-step authentication.
  • Plugins and themes that are out of date. The same guide says to make sure plugins are always updated and, if you are not using a plugin, to delete it from the system. It also says you should always keep up to date with the latest version of WordPress, because older versions are not maintained with security updates.
  • An open XML-RPC door nobody uses. The FBI's advice is to disable it if it is unused.
  • Dashboard file editing. The WordPress guide says the default dashboard lets administrators edit plugin and theme files, which it calls often the first tool an attacker will use once logged in, since it allows code execution. A single line in the configuration file turns that off. The guide is honest that this will not stop an attacker from uploading malicious files, only some attacks.

None of this is exotic. A site that was launched four years ago, with the agency's old login still active, a dozen plugins from a free trial and no one assigned to update them, is the profile these weaknesses describe. We would not say that profile is rare in Northeast Indiana. We have no data on how common it is.

A flat poster-style illustration on a navy background: an amber storefront with a teal striped awning and a big padlock on the front doors, while a side door at the back stands open and a trail of tiny amber dots leads to a faceless silhouette crouching by a fence

The illustration is a reminder of how this usually goes. The front door, your homepage and its contact form, is the part everyone looks at and the part that seems fine. The side door is a login nobody remembers, an unused plugin or an endpoint that was never turned off.

Why Might Your Own Site Look Fine to You?

This is the part that surprised us most. The FBI says the operation used a traffic distribution system, or TDS, that filtered content “by country, referrer, cookie, or IP address.” Google's description of redirects on hacked sites is similar: the kind of redirect sometimes depends on the referrer, user agent or device, so clicking a result in Google Search might take you to a suspicious page while visiting the same address directly from a browser does not. Relevant Audience adds, in a section it labels as its own analysis, that some of the campaigns it lists skip visitors who carry admin cookies. We could not confirm that last detail ourselves, so we pass it on as that site's reading.

What follows from this is our inference, not an FBI statement: a site owner who types the address into a browser, logged in, may be shown exactly the same site that was there last year.

What you see

You open your own address, logged in, from your office in Allen County. The homepage loads, the phone number is right and nothing looks off.

What a chosen visitor might see

Someone arrives from a Google result, from a country or network the attackers picked, with no admin cookie. Per the FBI's description of the traffic filtering, they can be shown different content than you.

The practical lesson is that a clean-looking homepage is weak evidence. Better evidence lives in places the attackers do not control as easily: the Search Console reports Google keeps about your site, the list of files and accounts on your hosting, and the update history of your plugins.

What Should You Look for in Search Console?

The one line in the FBI's protection table that crosses from security into marketing is this one. Under “Monitor search abuse,” it tells site owners to “review Search Console and webmaster tools for unrelated legal or business queries, sudden indexed pages, manual actions, and security warnings.” We read that as four separate checks:

  1. Unrelated queries. Open the Performance report and scan the list of search queries your site appears for. If an HVAC company starts showing up for a contract clause or a legal phrase, that is the pattern the FBI is describing. A dental office appearing for anything that is not dental, local or about the practice deserves a closer look.
  2. Sudden indexed pages. In the page indexing report, look for a jump in indexed pages or for addresses nobody on your team published. Google says page injection adds new pages while existing pages may look untouched.
  3. Manual actions. Google says sites that violate its spam policies may rank lower or not appear at all, and that human review can result in a manual action. Check the manual actions report for anything listed.
  4. Security warnings. The security issues report is where Google tells you what it found.
A floating dark dashboard panel with a teal glow: a flat teal line chart that suddenly spikes upward in amber at the far right, above a table where four rows have short gray bars and two rows have long amber bars marked with amber warning dots

The mockup above shows the shape of what you would hope to catch: a flat line that suddenly climbs, and a couple of rows in the query list that do not belong. Real reports look busier, and a spike has plenty of innocent explanations, such as a good week or a news story. A spike alone proves nothing. A spike for queries unrelated to your business is the part worth chasing. If you are already puzzled by traffic numbers that disagree between tools, our post on why Google Analytics and Search Console never match explains which tool answers which question.

What Does the FBI Say to Do if a Site Is Compromised?

The WordPress response section of the alert is three steps, and the order matters. The FBI says that when compromise is suspected you should:

  1. Place the site in a controlled maintenance state or restrict public access, while preserving a forensic copy of the files, database, logs and hosting configuration.
  2. Reset hosting panel, SSH, SFTP, WordPress administrator, database, API and CDN credentials from a clean system, and revoke active sessions and application passwords.
  3. Identify the initial access path, and restore from a known-clean backup only after removing the vulnerability or stolen credential that allowed entry.

The third step is the one that gets skipped. Restoring a backup feels like fixing the problem. The FBI's point is that if the way in is still open, the same attackers walk back through the same door. Do not rush to restore. First find out how they got in, whether that was a password, a plugin or an account. Also notice step one: save a copy before cleaning up, because the evidence is what lets anyone find the entry point.

The alert also asks that compromises be reported to the FBI, and lists the local field office, 1-800-CALL-FBI (225-5324) and ic3.gov in its reporting notice. That is a decision for the business owner, ideally with whoever manages the site.

The FBI's protection table also lists longer-term controls, including automatic updates for WordPress core and trusted plugins and themes where feasible, removing unused plugins, themes, accounts and staging sites, strong multi-factor authentication for administrators and hosting access, a web application firewall with login throttling, and file integrity monitoring that alerts on unexpected changes to plugin, theme, JavaScript, .htaccess and index files. It also recommends running PHP as a non-privileged account and denying PHP execution in the uploads folder. Those last two are server settings that belong with your host or developer. If you are on managed hosting, ask what they already do, because the answer varies. Our earlier post on what managed WordPress hosts do at the firewall shows how much a host can do without telling you.

What Does Your Staff Need to Know About Search Results?

The other half of the alert is about the person at the keyboard. According to Search Engine Roundtable's summary, the malware is particularly concerning because attackers use legitimate-looking search results and business-related documents to trick employees into downloading and executing malicious JavaScript files. The FBI's first Windows guidance is blunt about the moment of the download: if a suspicious archive was downloaded but not opened, do not extract or preview its contents, and record the download address, the search query, the time in the browser history and the file name.

If the JavaScript file was opened, the FBI says to disconnect network access and not to power off unless your incident response procedure requires it. It also says to change credentials from a separate, known-clean device and not from the suspected computer, and to reimage the endpoint when follow-on malware, credential theft or persistence is confirmed, because removing only the downloaded file does not restore trust. For a business with no IT staff, this is the point at which to call your IT provider, not to improvise.

The FBI's prevention list for Windows includes disabling Windows Script Host where business applications do not require it, using standard user accounts, and keeping Microsoft Defender, SmartScreen and tamper protection on. Whether to make those changes depends on the computers in your office, and we are not an IT department. But the habit we can suggest is simple and costs nothing:

  • Do not run a script or an archive you downloaded from a search result to get a form, template or small tool. Get business forms from the source that issues them, a vendor, a government site or your insurer, and download software from the maker's own page.
  • If a file ends in .js or arrives in a ZIP when you expected a document, stop and ask someone.
  • Tell staff that being a business with a lot of search traffic does not make a page safe. The poisoned pages rank next to legitimate resources, in the FBI's words.

This overlaps with a theme in our post on prompt injection and chatbot security: a tool that is helpful and trusting is the easy target. People are the same.

What Should a Fort Wayne Business Do This Month?

This list is ours, built from the FBI alert, Google's spam policies and the WordPress hardening guide. It is a first pass, not a full audit, and an unfamiliar plugin or account is a reason to ask your developer, not to delete things yourself.

  1. Find out who has the keys. Write down who can log in to your hosting, your domain account and WordPress. Remove the former web agency, the ex-employee and the freelancer from 2022. If you cannot say who manages the site, that is the finding.
  2. Turn on two-step sign-in for WordPress administrators and your hosting account, and replace any password that is short, reused or based on the company name.
  3. Update, then delete. Update WordPress core, plugins and the theme. Delete plugins and themes you are not using, in line with the WordPress guide. Take a backup first, because updates occasionally break things.
  4. Look at your administrator list. Every administrator account should belong to a person you can name. An account with a random-looking name is something to ask about, since Relevant Audience reports the FLASH links hidden admin users with random hex names to one of the campaigns.
  5. Ask about XML-RPC. Ask your developer whether xmlrpc.php is needed. If not, the FBI says to disable it. If it is, ask about rate limits.
  6. Open Search Console and check queries, indexed pages, manual actions and security issues, as described above. If your site is not verified in Search Console yet, set that up first.
  7. Check your backups. Know where the last clean backup is, how old it is and who can restore it. The FBI's advice assumes you have one.
  8. Brief your team on downloading files from search results, and tell them whom to call when something looks wrong.

If your site is not on WordPress, parts of this still apply, such as the account audit, two-step sign-in and backups, but the WordPress-specific items do not. We built our own site on a different stack, and we would not suggest rebuilding a working WordPress site because of one alert. Our earlier post on the React2Shell vulnerability covers the same lesson on a different platform: the risk follows the unpatched software, not the brand name.

What Does the FBI Alert Not Tell Us?

  • How many sites are still infected. The counts are dated October 2026. The FBI does not say how many sites have been cleaned up since.
  • Which plugins and themes. The alert says the administrator used stolen credentials to access vulnerable plugins and themes. It does not, as far as we can tell, name them or explain how each one was used.
  • Who the victims were by industry. It describes the search targeting as legal, and it does not list victims or break the figures down by state or city. We have no evidence that any Northeast Indiana business was involved.
  • What Google has done about it. The alert does not describe any change in Google ranking, indexing or warnings in response.
  • Whether you are affected. Only a check of your own site and accounts can say. We did not test anyone's website for this infection, and we read the primary document in full but are not security researchers.

We also found one small oddity in the PDF. Its narrative spells the file name “xlmrpc.php” in one place, while its protection table uses the correct “xmlrpc.php.” We have used the standard spelling throughout and assumed the first is a typo.

Want Someone to Check Who Can Log In to Your Website?

Button Block helps Northeast Indiana businesses keep their websites updated, locked down and findable. We can walk through your WordPress accounts, plugins, backups and Search Console reports and tell you what we see. We sell website maintenance and security services, so weigh our advice with that in mind.

Frequently Asked Questions

The FBI describes Gootloader as an initial access framework that uses a JavaScript malware loader, compromised websites and search engine optimization techniques to infect organizations. It says cyber actors used it as a ransomware precursor against victims across a wide variety of sectors. In plain terms, it is a way to get a first foothold inside a company, which other criminals can then use to attack it.
As of October 2026, the FBI said it had identified over 1,000 infected WordPress sites and 216 domains controlled by the Gootloader administrator. It tied that activity to over $28 million in ransomware payments. The FBI does not say how many of those sites are still compromised today.
We cannot say, and the FBI does not give odds. What the alert shows is that the attackers wanted ordinary, legitimate WordPress sites to use as lure pages, redirectors and relay points, and that they got in by guessing or stealing credentials and by using vulnerable plugins and themes. A small business site that is old, unmaintained or protected by a weak password has the same weaknesses the alert describes, whatever the owner's trade.
Possibly not. The FBI says the operation used a traffic distribution system that filtered content by country, referrer, cookie or IP address. Google describes a similar pattern for hacked sites, where clicking a result sends you somewhere suspicious but visiting the same address directly does not. Looking at your homepage while logged in is not a reliable check. Search Console data and a review of the site's files and accounts are better evidence.
XML-RPC is a standard WordPress API endpoint, the file xmlrpc.php, that the FBI says attackers frequently target for brute-forcing credentials. The FBI's advice is to disable it if it is unused. If something you rely on needs it, such as an older app that connects to the site, the FBI says to rate-limit it, allow only the methods you need and monitor sign-in attempts. Ask whoever manages your site whether anything uses it before you switch it off.
Start with whoever hosts and manages the site, because the first steps involve your hosting account. The FBI's reporting notice says suspected Gootloader intrusions can be reported to your local FBI field office, at 1-800-CALL-FBI (225-5324), or through ic3.gov. It also asks you to keep the incident information and any evidence you have.
What is Gootloader?
The FBI describes Gootloader as an initial access framework that uses a JavaScript malware loader, compromised websites and search engine optimization techniques to infect organizations. It says cyber actors used it as a ransomware precursor against victims across a wide variety of sectors. In plain terms, it is a way to get a first foothold inside a company, which other criminals can then use to attack it.
How many WordPress sites did the FBI say were infected?
As of October 2026, the FBI said it had identified over 1,000 infected WordPress sites and 216 domains controlled by the Gootloader administrator. It tied that activity to over $28 million in ransomware payments. The FBI does not say how many of those sites are still compromised today.
Is my small business website a likely target?
We cannot say, and the FBI does not give odds. What the alert shows is that the attackers wanted ordinary, legitimate WordPress sites to use as lure pages, redirectors and relay points, and that they got in by guessing or stealing credentials and by using vulnerable plugins and themes. A small business site that is old, unmaintained or protected by a weak password has the same weaknesses the alert describes, whatever the owner's trade.
Will I see the problem if I open my own homepage?
Possibly not. The FBI says the operation used a traffic distribution system that filtered content by country, referrer, cookie or IP address. Google describes a similar pattern for hacked sites, where clicking a result sends you somewhere suspicious but visiting the same address directly does not. Looking at your homepage while logged in is not a reliable check. Search Console data and a review of the site's files and accounts are better evidence.
What is XML-RPC and do I need to turn it off?
XML-RPC is a standard WordPress API endpoint, the file xmlrpc.php, that the FBI says attackers frequently target for brute-forcing credentials. The FBI's advice is to disable it if it is unused. If something you rely on needs it, such as an older app that connects to the site, the FBI says to rate-limit it, allow only the methods you need and monitor sign-in attempts. Ask whoever manages your site whether anything uses it before you switch it off.
Who should I contact if I think my site was hacked?
Start with whoever hosts and manages the site, because the first steps involve your hosting account. The FBI's reporting notice says suspected Gootloader intrusions can be reported to your local FBI field office, at 1-800-CALL-FBI (225-5324), or through ic3.gov. It also asks you to keep the incident information and any evidence you have.

Sources & Further Reading

  • FBI FLASH CC-111626-MW, “Gootloader Malware Using SEO Poisoning and Compromised Websites to Gain Initial Access” (November 16, 2026): ic3.gov (read November 21, 2026): the 1,000 sites, 216 domains and $28 million figures, the description of the operation, the WordPress response steps, the protection table and the reporting notice. We read the full 10 page document.
  • Search Engine Roundtable, “FBI: SEO Poisoning Led To $28 Million In Ransomware Payments” (November 16, 2026): seroundtable.com (read November 21, 2026): the news report, the quoted FBI paragraph, the Bill Hartzer remark and the note that the technique is not new. We read the full article.
  • Relevant Audience, “FBI: Gootloader SEO poisoning hit 1,000+ WordPress sites” (November 18, 2026): relevantaudience.com (read November 21, 2026): the table of other WordPress campaigns in the FLASH, the Search Console checks and the list of what the alert leaves out. We read the whole article and did not verify its campaign figures against the PDF.
  • Google Search Central, “Spam policies for Google web search”: developers.google.com (read November 21, 2026): the definition of hacked content, the four examples and the statement on manual actions. We read the introduction and the hacked content section.
  • WordPress Developer Resources, “Hardening WordPress” (last modified October 14, 2026): developer.wordpress.org (read November 21, 2026): the guidance on updates, passwords and two-step authentication, plugins, and disabling dashboard file editing. We read the sections we cite.