The FBI just tied over 1,000 hacked WordPress sites to $28 million in ransom payments

The FBI released a FLASH alert on 16 November, numbered CC-111626-MW and marked TLP:CLEAR, on the Gootloader malware framework. The headline number is the one that will travel: as of October 2026 the Bureau counted over 1,000 infected WordPress sites and 216 domains run by the Gootloader administrator, and tied that infrastructure to more than $28 million in ransomware payments. What makes it worth an agency’s attention is not the malware analysis — it is that the sites doing the damage are ordinary client sites whose owners have no idea they are involved, which is the entire argument for keeping an inventory and a patching routine across every site you look after.

What the alert actually says

  • Gootloader is an initial access framework, not ransomware itself — JavaScript loader, compromised websites, SEO
  • The FBI has tracked it from 2020 to 2026, with the 2025–2026 phase described as abusing WordPress comment paths, geofencing and traffic distribution services
  • Compromised WordPress sites are used as lure pages, redirectors, traffic filters or relay infrastructure — the site is the delivery network, not the target
  • The operator scanned WordPress sites for `xmlrpc.php`, then used compromised credentials to get in, reaching vulnerable plugins and themes, injected posts, XML-RPC, REST routes and modified JavaScript
  • A traffic distribution system filters visitors by country, referrer, cookie or IP, so the poisoned page often will not render for you when you go looking for it

The targeting is unusually specific

Search terms were tuned for practicing attorneys, in-house counsel, law firm partners, litigation and privacy teams, legal operations staff, general counsel and legal technology decision makers. The method is long-tail: low-competition phrases like jurisdiction-specific contract clauses, where a planted page can outrank almost nothing and still land on page one. The alert prints a sample keyword list — “zoning government definition”, “when was divorce legalized in korea” — and the hidden link blocks used to prop them up.

If a client is in legal services, this is a sector alert. If they are not, they can still be the host.

There is no CVE to patch here

Worth being blunt about, because it changes what you do with the information. The FBI does not name a vulnerability. The access path is stolen credentials plus XML-RPC brute forcing plus whatever outdated plugin or theme was sitting there. You cannot close this with an update run. It closes with credential hygiene, MFA on admin and hosting, XML-RPC disabled where nothing uses it, and file integrity monitoring that notices a new mu-plugin or a changed `index.php`.

The rest of the alert is a free competitive audit

The FBI includes a table of other campaigns currently abusing WordPress at scale, which is a useful sanity check on how common this is:

  • SocGholish (TA569), TA2726, Parrot TDS — Operation Endgame took down 106 servers and cleaned 14,971 WordPress sites in June 2026; 1,509 sites were still active April–July 2026
  • StopAndProtect — thousands of sites, found mid-May 2026, hidden must-use plugins plus a concealed REST upload endpoint with hard-coded credentials
  • DollyWay — 20,000+ sites since 2016, 10,000+ still active February 2025, hidden admin users with random hex names, reinfects on every page load
  • ClearFake — active September 2026, payload pulled from blockchain smart contracts, so it changes without anyone touching the site again
  • “DoubleDonut” — 250+ sites in 12 countries, and notably skips visitors carrying admin cookies, so the person most likely to notice never sees it

The hardening table, in agency terms

The FBI’s WordPress protection list is essentially a maintenance scope. The items that actually get skipped in practice:

  • Maintain a complete software inventory. Remove unused plugins, themes, accounts, staging sites. Old staging copies are the ones that get forgotten and left unpatched
  • Disable `xmlrpc.php` if unused. If something needs it, rate-limit and monitor POST volume
  • Deny PHP execution under `wp-content/uploads`. Cheap, almost never done
  • Separate hosting accounts per site so one compromised site cannot write another site’s files — the multi-site-on-one-cPanel problem every agency inherits at some point
  • Compare core files against official checksums, and alert on unexpected plugin, theme, mu-plugin, JavaScript, `.htaccess` and index-file changes
  • Check Search Console for indexed pages and search queries that have nothing to do with the client’s business. This is often the first visible symptom, and it shows up in a tool the client already has open

That last one is the practical tell. A marketing agency looking at a client’s Search Console is better positioned to catch this than most security tooling, because unrelated legal queries appearing in a plumber’s impressions report is obvious the moment someone looks.

If you think a site is already in it

The FBI’s response order matters: preserve a forensic copy first, reset hosting panel, SSH, SFTP, admin, database, API and CDN credentials from a clean machine, revoke active sessions and application passwords, then identify the initial access path. Restoring from backup before you have found how they got in just reinstates the hole.

What this means for Codelibry clients

If your sites are on one of our maintenance plans, the controls this alert asks for — inventory, core and plugin patching, XML-RPC handling, admin access rules and file integrity checks — are already part of the standing routine, and their status turns up in your monthly maintenance report. There is nothing you need to action from this. If you are not on a plan, this is the gap the plan is built to close: the sites in that FBI count were not targeted for who their owners are, they were simply reachable and unwatched, and nobody noticed for months.

Source: FBI Internet Crime Complaint Center

Vitalii Omelchenko
Founder at Codelibry and WordPress enthusiast. Helping digital agencies to protect their margins and do better at website delivery.Need help with wordpress builds? Book a call using the Contact page
our Blog

Explore our Latest Insights

A fake Cloudflare check can install a WordPress backdoor using your own admin session
News
November 18, 2026
319 WordPress plugin vulnerabilities in one week. Fourteen were critical and one is still unpatched
News
October 2, 2026
The WordPress backdoor that rebuilds itself. Deleting the files is not a cleanup
News
October 2, 2026
whatsapp icon