FBI: hacked WordPress sites used as search lures
The FBI says Gootloader used hacked WordPress sites and SEO to reach victims. What a local business should check.
On November 16, 2026, the FBI published FLASH CC-111626-MW, "Gootloader Malware Using SEO Poisoning and Compromised Websites to Gain Initial Access."
The FBI calls Gootloader "an initial access framework that uses a JavaScript malware loader, compromised websites, and search engine optimization (SEO) techniques to infect organizations." Actors used it as a ransomware precursor across many sectors. As of October 2026, the FBI had identified over 1,000 infected WordPress sites and 216 domains controlled by the Gootloader administrator. It says those sites and domains led to over $28 million in ransomware payments.
The searches were written for lawyers and legal teams. The hacked page can sit on any WordPress site the attackers took over, including a plumber, a dentist, a roofer, or a lawyer.
What the FBI says happened
From 2020 through 2026, the FBI says Gootloader reached organizations through search phrases with little competition. A footnote defines that as low search volume, so a narrow keyword is easier to target. The example is a jurisdiction-specific contract clause. With that SEO, actor-controlled pages appeared next to legitimate resources.
The FLASH says the terms targeted practicing attorneys, in-house counsel, law firm partners, litigation and privacy teams, legal operations staff, general counsel, and legal-technology decision makers. For 2025 and 2026 it describes a U.S. legal focus, abuse of WordPress comment paths, geofencing, and traffic-distribution services.
Compromised WordPress sites then worked as lure pages, redirectors, traffic filters, or relay infrastructure. Hidden keyword links and arranged backlinks made the lures easier to find. The administrator used stolen credentials to reach vulnerable plugins and themes. The compromises also involved injected posts, XML-RPC, REST routes, and modified JavaScript.
The FBI says the administrator scanned WordPress sites for a file the FLASH spells xlmrpc.php. The footnote identifies WordPress's XML-RPC endpoint, "frequently targeted by attackers for brute-forcing credentials." The protection table says to disable xmlrpc.php if the site does not use it. A traffic distribution system filtered content by country, referrer, cookie, or IP address.
The FBI also describes DollyWay, a separate campaign on 20,000 or more WordPress sites since 2016. It cites hidden admin users with random hexadecimal names, redirects to scam pages, and reinfection on every page load. An admin name nobody on staff created is a reason to get help.
What a local owner should do with that
This section is our guidance.
A law firm or a trades company gets calls because the domain looks ordinary. A lure on that domain can send a stranger somewhere they did not mean to go. The Search Console reports below are where a browser warning or a removal from results would show up. The $28 million is the FBI's ransomware total for the campaign.
Because the filter depends on country, referrer, cookie, or IP address, your own visit can look fine. Our spider simulator shows the title, text, and links from one fetch. Our redirect checker lists each hop and status code. Legal phrases you never wrote, or a hop to a domain you do not control, is a reason to limit public access and call the host.
What to look for in Search Console
The FBI's list includes "Monitor search abuse": review Search Console and webmaster tools for unrelated legal or business queries, sudden indexed pages, manual actions, and security warnings. If you are in Search Console for the November core update, that is a separate question. Our story on reading that traffic covers the rollout.
Unrelated queries. Google's Performance report shows queries that displayed the site, plus clicks and impressions, on the Queries tab. Contract clauses on a plumbing site match the pattern the FBI describes. Google says you may be unable to reproduce a listed query, because results depend on time, place, device, and recent search history.
Indexed pages. Google's Page indexing report shows a graph and a count of indexed and not-indexed URLs. A rise you did not publish is the "sudden indexed pages" item. Google says to use this report for the sitewide picture and URL Inspection for one address.
Security Issues. Google's Security issues report lists findings when Google decides a site was hacked or could harm a visitor: hacked content, malware and unwanted software, and social engineering (content that tricks someone into revealing information or downloading software). Affected pages can show a warning in results or in the browser. No findings is a green check, and the sample URLs are only a sample.
Manual Actions. Google's Manual actions report shows a human reviewer's action when pages break spam policies. Google says most address attempts to manipulate the index, and that some or all of the site will not appear in search results. No actions is a green check.
Hardening steps the FBI lists
From the protection table in the same FLASH:
- Update WordPress core and trusted plugins and themes automatically where you can. Use virtual patching for an emergency exposure.
- Remove unused plugins, themes, accounts, staging sites, and default components. Keep a software inventory.
- Require phishing-resistant multifactor authentication, or strong MFA, for administrators and hosting access. Use single sign-on or a VPN restriction where practical.
- Disable
xmlrpc.phpif unused. If you need it, rate-limit it, allow only required methods or trusted integrations, and watch authentication and POST volume. - Run PHP as a low-privilege account, make core files read-only where practical, and deny PHP execution under
wp-content/uploads. - Separate hosting accounts and sites, limit database permissions, protect
wp-config.php, and keep one site from writing another's files. - Use managed firewall rules, bot protection, login throttling, upload controls, and alerts for new REST endpoints or unusual admin-ajax actions. Google's post on CDN moves and Googlebot says a blanket bot challenge that also stops Googlebot can push pages out of Search, so allow verified crawlers. Local detail is in this story.
- Compare core files with official checksums. Alert on unexpected changes to plugins, themes, must-use plugins, JavaScript,
.htaccess, and index files. - Review the Search Console items above.
- Keep access, firewall, login, control-panel, SFTP or SSH, database, DNS, and outbound logs off the web server.
If you already suspect a problem
If a WordPress compromise is suspected, the FBI says to restrict public access, keep a forensic copy of the files, database, logs, and hosting setup, and reset hosting, SSH, SFTP, administrator, database, API, and CDN credentials from a clean computer. Revoke sessions and application passwords. Restore a known-clean backup only after the vulnerability or stolen credential is gone.
If someone downloaded a suspicious archive, the FBI says not to open or preview it, and to record the URL, query, time, and filename. If a JavaScript file was opened, disconnect that computer, leave it on unless the incident plan says otherwise, and change passwords from a different clean device.
Report suspected cases to a local FBI field office, at 1-800-CALL-FBI (225-5324), or at www.ic3.gov. Include the date, time, what you saw, the systems affected, the organization name, and a contact when you have them. Keep logs and any ransom note. Reporting is voluntary. For the owner, the monthly version is trusted updates, MFA on WordPress and at the host, and a Search Console look for queries and pages that are not the business.
Sources
- FLASH CC-111626-MW: Gootloader Malware Using SEO Poisoning and Compromised Websites to Gain Initial Access
- Security issues report (Search Console Help)
- Manual actions report (Search Console Help)
- Performance report for Search results (Search Console Help)
- Page indexing report (Search Console Help)
- Moving to a CDN without overwhelming your origin (or blocking Googlebot)