Back to the homepage
Technical SEO

How to Check a SaaS WordPress Site for SEO Poisoning After the FBI's Gootloader Warning

The FBI's November 2026 FLASH alert tied SEO poisoning to compromised WordPress sites. Here is how a B2B SaaS team can audit search data and WordPress for injected pages.

Grant Whitaker · Technical SEO Writer
Start reading ↓
Desk
Technical SEO
Format
How-to
Reading time
7 min
Published
Nov 17, 2026

Treat the FBI's November 16, 2026 Gootloader alert as a prompt to audit your WordPress marketing site. Check Search Console for queries and indexed pages you never targeted. Look for unknown admin users, must-use plugins and posts. Update plugins, require strong MFA, disable XML-RPC if unused, and report a suspected compromise to the FBI.

This guide is for B2B SaaS marketers, founders and web leads who run a WordPress blog or marketing site. It covers what the FBI reported, how to spot poisoned pages through search data, what to inspect inside WordPress, and how to respond. cekpr covers technical SEO for software companies, and a hacked page is a technical SEO problem first.

What did the FBI say about SEO poisoning and WordPress?

The FBI said attackers used Gootloader malware, compromised websites and search engine optimization to gain access to organizations. As of October 2026, the agency counted over 1,000 infected WordPress sites and 216 domains tied to the operator. It linked the activity to more than $28 million in ransomware payments.

anonymous, collective, secret, hacker

The details come from the FBI's FLASH alert CC-111626-MW. It says actors targeted search phrases with little competition, such as a jurisdiction-specific contract clause. Their pages then appeared beside legitimate results. The operator scanned WordPress sites for xmlrpc.php and later used compromised credentials to get in.

Compromised sites played several roles. They served as lure pages, redirectors, traffic filters or relay points. The FBI also described hidden keyword links and arranged backlinks that raised the lure pages' visibility. A traffic distribution system filtered visitors by country, referrer, cookie or IP address, so the owner often saw nothing wrong.

The campaign focused on legal professionals and legal technology buyers. That should get the attention of legal-tech SaaS companies. Any WordPress site with weak credentials can host the lure, though. Your domain's reputation is the asset being borrowed.

How can a SaaS site tell if it hosts poisoned pages?

Start in Search Console, because poisoned pages leave search footprints. The FBI's own advice includes reviewing webmaster tools for unrelated legal or business queries, sudden indexed pages, manual actions and security warnings. Work through the checks below in order.

web, internet, symbol, webdesign
  1. Open the Performance report and sort queries by impressions. Look for terms unrelated to software, such as contract clauses or betting.
  2. Filter by page and look for URLs you did not publish, especially old-looking dated paths.
  3. Open the Pages report and compare the indexed count with last month. A sudden jump needs an explanation.
  4. Check Manual actions and the Security issues report for hacked content or malware flags.
  5. Search Google for your domain plus unrelated words, then open results from a private window.

That last step matters. Because of the filtering, a lure page may hide from logged-in admins and from direct visits. Reach it the way a victim would, by clicking a Google result. Do not download anything it offers.

Context also matters. Teams may read odd traffic jumps as a ranking win. During an update, that mistake is easy. Our plan for the November 2026 core update shows how to separate real movement from noise, and unexplained queries should be ruled out as injected content first.

Use this table to sort search symptoms by likely cause before you decide on a response:

How can a SaaS site tell if it hosts poisoned pages?
SymptomPossible causeFirst check
Impressions for legal or betting termsInjected lure pagesPerformance report, by page
Indexed page count jumpsInjected posts or auto-generated URLsPages report and sitemap
Rankings shift on known pagesCore update or content changeChange log and update dates
Browser or search warningMalware or hacked content flagSecurity issues report

Why does SEO poisoning matter to a B2B SaaS brand?

It matters because buyers vet software vendors through search. Google says pages or sites affected by a security issue can appear with a warning label in results, or behind a browser warning page. Either one stops a prospect from reaching your demo page. Rankings recover slowly after a security flag, so prevention costs less than cleanup.

The risk also reaches your own staff. The FBI says attackers used business-style documents and search results that looked legitimate to trick employees into running malicious JavaScript. A salesperson who searches for a contract template and downloads an archive is a target. Brief your team on this, and tell them to report odd downloads rather than hide them.

What should you inspect inside WordPress?

Inspect users, plugins, posts and scripts, because the FBI's examples show attackers hiding in all four. The agency's table of related WordPress campaigns lists hidden admin users with random hex names and concealed must-use plugins. It also lists fake plugins and hidden REST API endpoints.

man, computer, screen, desktop

Use this checklist on a staging copy or with read-only access when possible:

  • Users: list every administrator and delete accounts nobody can explain.
  • Must-use plugins: open the wp-content/mu-plugins folder, which does not appear in the normal plugin screen.
  • Plugins and themes: remove anything unused, and compare core files with official checksums.
  • Posts and comments: look for injected posts and unusual comment paths.
  • Scripts and .htaccess: scan for unfamiliar JavaScript and redirect rules.

The comment path point connects to spam control. Our guide to preventing user-generated spam on a SaaS site covers the moderation side. The FBI reports that Gootloader abused WordPress comment paths in 2025 and 2026, so loose comment settings carry more risk than they appear to.

Hidden links deserve a check of their own. Attackers inserted keyword links and built backlinks to lift lure pages. A site owner can run a similar review of outbound links. Our backlink audit for the September 2026 spam update explains how to review link profiles for patterns that should not be there.

Which WordPress controls reduce the risk most?

The FBI lists ten technical protections for WordPress. A small SaaS team can start with five of them. The table pairs each control with a concrete step.

Which WordPress controls reduce the risk most?
FBI controlWhat it meansStep for a SaaS team
PatchingUpdate core, plugins and themesTurn on automatic updates for trusted plugins
Reduce attack surfaceRemove unused componentsDelete idle plugins, themes and staging sites
Protect administrationStrong MFA for admins and hostingRequire MFA on WordPress and the host
Restrict XML-RPCDisable it if unusedBlock xmlrpc.php at the server or firewall
Monitor integrityAlert on unexpected file changesWatch mu-plugins, .htaccess and index files
dsgvo, data collection, data security, data protection regulation

On MFA, not every method is equal. The Cybersecurity and Infrastructure Security Agency (CISA) calls phishing-resistant MFA the gold standard and urges administrators to adopt it. The FBI asks for phishing-resistant or strong MFA on WordPress and hosting accounts. Use hardware keys or passkeys where the host supports them.

The FBI also advises running PHP as a non-privileged account and denying PHP execution under wp-content/uploads. Ask your host or developer to confirm both. At cekpr, we treat a blocked uploads folder as the cheapest control on this list.

XML-RPC needs a note. Some integrations still use it, so a blanket block can break them. The FBI says to disable xmlrpc.php if you do not use it. If you do, it advises rate limits, an allowlist of necessary methods or trusted integrations, and monitoring of login and POST volume.

What should you do if you find injected pages?

Contain first and clean second. The FBI recommends putting the site in a controlled maintenance state while you preserve a forensic copy of files, database, logs and hosting configuration. Cleaning before copying destroys the evidence you need to find the entry point.

  1. Preserve a copy of files, the database, logs and the hosting configuration.
  2. Reset hosting panel, SSH, SFTP, WordPress admin, database, API and CDN credentials from a clean device.
  3. Revoke active sessions and application passwords.
  4. Find the initial access path.
  5. Restore from a known-clean backup only after you close that path.

Restoring a backup without fixing the stolen credential or vulnerable plugin invites reinfection. After cleanup, fix issues across the whole site. Google's Search Console help says that once all issues are fixed on all pages, you can select Request Review in the Security Issues report and describe your fixes.

If an employee already downloaded a file, act quickly. The FBI says not to extract or preview a suspicious archive and to submit it through your security process. If the JavaScript file was opened, disconnect the device from the network. Do not power it off unless your incident plan says so. Change credentials from a separate, known-clean device.

The FBI encourages suspected Gootloader intrusions to be reported to a local field office or to its Internet Crime Complaint Center. Keep logs, exposed credentials and any extortion messages. Also tell your hosting provider, and check every other site on the same hosting account.

How often should a SaaS team repeat this audit?

Repeat the search checks monthly and the WordPress checks every quarter. Add alerts for new administrators and file changes so the audit is not the only control. Treat the FBI's alert as a baseline, not a one-time scare. Attackers keep changing their paths, but weak credentials and old plugins remain the usual way in.

What is SEO poisoning?
SEO poisoning is when attackers rank malicious or deceptive pages for search terms so that visitors find them. In the FBI's Gootloader alert, actors used compromised WordPress sites and low-competition queries so their lure pages appeared next to legitimate resources. The aim was to trick people into running malicious JavaScript.
Can a B2B SaaS marketing site be used in a Gootloader-style attack?
Yes, if it runs WordPress with weak credentials or vulnerable plugins. The FBI describes compromised WordPress sites acting as lure pages, redirectors, traffic filters or relay infrastructure. The search targeting it reported was aimed at legal professionals, but the hosting side only needs a site the attackers can enter.
How do I find hidden pages I never published?
Review the Search Console Performance report by page and query for unrelated terms, then compare the Pages report's indexed count with last month. Search Google for your domain plus unrelated words and open results from a private window, because lure pages can hide from logged-in administrators and direct visits.
Should I disable XML-RPC on my WordPress site?
Disable it if you do not use it, which is the FBI's guidance. If a plugin or integration needs it, rate-limit requests, allow only the necessary methods or trusted integrations, and monitor login and POST volume. Test the change on a staging copy first so you do not break connected tools.

Written by

Grant Whitaker

Grant covers crawling, indexing and link audits for B2B software sites. He writes the step-by-step guides engineers and marketers can both follow.

More from Grant
Up next · Measurement How to Pull Branded and Non-Branded SaaS Search Data From the Search Analytics API
The Thursday letter · free

join the club.

The week's best SEO and AI search posts, plus one thing to check in your own Search Console, every Thursday morning. Unsubscribe whenever.