The short answer

On November 16, 2026, the FBI published a FLASH alert (CC-111626-MW) on Gootloader, a malware operation that hides download lures on hacked WordPress sites and pushes them into search results. As of October 2026 the FBI had identified more than 1,000 infected WordPress sites and 216 attacker-controlled domains, and links the operation to over $28 million in ransomware payments. Attackers got in by scanning for xmlrpc.php, using stolen credentials, and abusing vulnerable plugins and themes. Your site does not have to be a law firm or rank for anything valuable to be used. The fastest checks are in Google Search Console: unrelated legal or business queries, a sudden jump in indexed pages, manual actions, and security warnings. Then review admin users, plugins, the mu-plugins folder, and XML-RPC, and turn on multi-factor sign-in.

A smiling woman reviews a website dashboard on a laptop at an office desk.

What the FBI and DOJ announced

The FBI FLASH, coordinated with CISA and marked TLP:CLEAR so it can be shared freely, describes Gootloader as "an initial access framework that uses a JavaScript malware loader, compromised websites, and search engine optimization (SEO) techniques to infect organizations." It is not ransomware itself. It gets attackers onto a victim’s computer, and that access is then used for ransomware. The FBI says that as of October 2026 it had identified "over 1000 infected WordPress sites and 216 domains controlled by the Gootloader administrator, which led to over $28 million in ransomware payments."

Four days earlier, on November 12, the Justice Department announced that it had removed Gootloader malware from over 100 servers, "including compromised WordPress sites," and seized U.S. domains used to deliver and control it. DOJ says Gootloader has infected at least 25,000 computers since 2018 and was used in ransomware attacks on at least 44 U.S. victims, with approximately $28.8 million in losses. The operation was part of the multinational Operation Endgame. The takedown does not clean every hacked site, which is why the FBI followed with detection and hardening guidance for site owners.

How hacked WordPress sites were used

According to the FLASH, between 2020 and 2026 the operation targeted low-competition search phrases, such as a jurisdiction-specific contract clause, so its pages could appear next to legitimate results. Most targets were legal professionals: attorneys, in-house counsel, and legal technology buyers. Someone searching for a document landed on a hacked site and was offered a download that carried the malware.

The FBI lists how the administrator used WordPress:

  • Finding sites. It scanned WordPress sites for xmlrpc.php, a standard endpoint often targeted for password guessing, and later used compromised credentials to get in.
  • Getting deeper access. It used stolen credentials to reach vulnerable plugins and themes, then injected posts, XML-RPC and REST routes, and modified JavaScript. In 2025 and 2026 it also abused WordPress comment paths.
  • Giving each site a job. Hacked sites acted as lure pages, redirectors, traffic filters, or relay infrastructure.
  • Ranking the lures. Hidden keyword links and arranged backlinks between sites pushed the lure pages up in search.
  • Hiding from owners. A traffic distribution system filtered visitors by country, referrer, cookie, or IP address.

That last point is why many owners never notice. If you visit your own home page, you may see nothing wrong. The FLASH also lists other campaigns that abuse WordPress the same way, including one that skips visitors with admin cookies and one, DollyWay, that the FBI says has hit more than 20,000 sites since 2016 using fake must-use plugins and hidden admin users with random hex names.

Why a small business site is a target

The operation did not need your site to rank for valuable keywords. It needed a working login, an outdated plugin, or an open XML-RPC endpoint, and then it borrowed your domain’s reputation in Google. The people harmed are the visitors who download the lure, but the site owner pays too: search traffic for unrelated spam pages, possible manual actions or browser warnings, and the cost of a cleanup.

How to check your WordPress site

These checks follow the FBI’s WordPress guidance. Most take a few minutes.

  1. Search Console. The FBI specifically recommends reviewing Search Console for "unrelated legal or business queries, sudden indexed pages, manual actions, and security warnings." Look at Performance, then Queries, for phrases you never wrote about. Check the Pages report for a jump in indexed URLs, and open Manual actions and Security issues.
  2. Admin users. Under Users, filter by Administrator. Remove anyone you do not recognize, especially accounts with random-looking names.
  3. Plugins and must-use plugins. Remove unused plugins and themes. Ask your host or developer to look in wp-content/mu-plugins, which WordPress loads automatically and does not show on the normal Plugins page.
  4. Core file integrity. The FBI recommends comparing core files with official checksums and alerting on unexpected plugin, theme, mu-plugin, JavaScript, .htaccess, and index file changes. WP-CLI’s checksum command or a security plugin can do this.
  5. XML-RPC. Disable xmlrpc.php if nothing uses it. If an app or integration needs it, rate-limit it, allow only the methods it uses, and watch login and POST volume.
  6. Sign-in. Require multi-factor authentication for WordPress administrators and for your hosting account. The FBI recommends phishing-resistant MFA where possible.
  7. Logs. Keep web, login, hosting panel, and database logs somewhere other than the web server, so an attacker cannot erase them.

The FLASH adds server-side hardening that your host or developer should handle: run PHP as a non-privileged account, deny PHP execution under wp-content/uploads, separate sites so one cannot write another’s files, protect wp-config.php, and use a web application firewall with login throttling and alerts for new REST endpoints.

If you find signs of compromise

The FBI’s response steps, in plain terms:

  • Put the site in maintenance mode or restrict access, but first keep a copy of the files, database, logs, and hosting settings.
  • From a clean computer, reset hosting panel, SSH, SFTP, WordPress administrator, database, API, and CDN credentials. Log out all sessions and revoke application passwords.
  • Find how the attacker got in. Restore from a known-clean backup only after you have removed that vulnerability or stolen credential, or the site will be reinfected.
  • Report suspected Gootloader activity to your local FBI field office or the FBI Internet Crime Complaint Center.

Also this week: TRUST#GRAFT

A separate campaign shows why "remove the plugin and change the password" is not always enough. In SC Media on November 17, Securonix’s head of threat research described TRUST#GRAFT, where malicious JavaScript on a WordPress page waits for a logged-in administrator and uses that browser session to upload and activate a fake plugin called Web Media Optimizer. The plugin hides from normal plugin lists and tries to copy itself into the must-use folder as wmedia-recovery.php. Securonix recommends doing admin work in a dedicated browser profile, reviewing public pages in a separate logged-out one, and limiting who can install plugins.

What to do next

  1. Open Search Console today and check queries, indexed pages, manual actions, and security issues.
  2. Review administrator accounts and turn on MFA for WordPress and your host.
  3. Remove unused plugins and themes, and keep the rest updated. Our WordPress Maintenance plans cover updates and monitoring.
  4. If something looks wrong, preserve evidence before cleaning. Our WordPress Rescue service handles hacked-site cleanups.

FAQ

What is Gootloader?

Gootloader is an initial access framework that uses a JavaScript malware loader, hacked websites, and SEO techniques to infect people who search for documents. The FBI says it was used as a precursor to ransomware. It is not ransomware itself.

How many WordPress sites did Gootloader use?

The FBI's November 16, 2026 FLASH says that as of October 2026 it had identified more than 1,000 infected WordPress sites and 216 domains controlled by the Gootloader administrator, linked to over $28 million in ransomware payments.

How did Gootloader get into WordPress sites?

Per the FBI, it scanned for xmlrpc.php, used compromised or stolen credentials, abused vulnerable plugins and themes, and injected posts, XML-RPC and REST routes, and modified JavaScript. It later also abused WordPress comment paths.

How can I tell if my WordPress site was used for SEO poisoning?

Check Google Search Console for unrelated legal or business queries, a sudden increase in indexed pages, manual actions, and security warnings, as the FBI recommends. Also review admin users, plugins, the mu-plugins folder, and core file checksums.

Should I disable XML-RPC in WordPress?

The FBI recommends disabling xmlrpc.php if it is unused. If an app or integration needs it, rate-limit it, allow only necessary methods, and monitor authentication and POST volume.

Did the DOJ takedown fix infected sites?

Not all of them. On November 12, 2026, DOJ said it removed Gootloader from over 100 servers, including compromised WordPress sites, and seized domains. The FBI still asks site owners to check for and remove compromises.

Sources

  1. FBI FLASH CC-111626-MW, "Gootloader Malware Using SEO Poisoning and Compromised Websites to Gain Initial Access" (November 16, 2026). https://www.ic3.gov/CSA/2026/261116.pdf
  2. U.S. Department of Justice, "Gootloader Malware Disrupted in International Cyber Operation" (November 12, 2026). https://www.justice.gov/opa/pr/gootloader-malware-disrupted-international-cyber-operation
  3. SC Media, "How TRUST#GRAFT uses a WordPress admin session to install a backdoor" (November 17, 2026). https://www.scworld.com/perspective/how-trustgraft-uses-a-wordpress-admin-session-to-install-a-backdoor
  4. Search Engine Roundtable, "FBI Says SEO Poisoning Led To $28 Million In Ransomware Payments." https://www.seroundtable.com/fbi-says-seo-poisoning-led-to-28-million-in-ransomware-payments-42546.html