Gootloader WordPress Sites: FBI Warns of Ransomware

gootloader-wordpress-sites-fbi-flash

The FBI warns that Gootloader WordPress sites have become a delivery network for ransomware access. In a FLASH dated November 16, it counts more than 1,000 infected WordPress sites and 216 domains run by the Gootloader administrator as of October, which the FBI says led to over $28 million in ransomware payments. A search for a contract template can end with an employee running malware.

What Happened With the Gootloader WordPress Sites

FLASH CC-111626-MW, coordinated with CISA, describes Gootloader as an initial access framework: a JavaScript loader, compromised websites and search engine optimization. Between 2020 and 2026, the operators targeted searches with little competition, such as a jurisdiction-specific contract clause, so their pages ranked next to legitimate ones. Since 2025 the main target has been US legal professionals.

The hijacked WordPress sites serve as lure pages, redirectors, traffic filters or relay points. The administrator scanned WordPress sites for the XML-RPC file, later used compromised credentials to get in, and used stolen credentials to reach vulnerable plugins and themes. Posts, XML-RPC, REST routes and JavaScript were changed. The traffic distribution system filters visitors by country, referrer, cookie or IP address, so a site owner may see nothing unusual.

A visitor who opens the downloaded JavaScript file, delivered in a ZIP, starts the chain: Windows Script Host, PowerShell, scheduled tasks and payloads stored in the registry. Later steps include AMSI patching, pass-the-hash, Kerberoasting and lateral movement over WinRM and SMB. The FBI describes Gootloader as a ransomware precursor across many sectors. No CVE applies, and this FLASH names no ransomware group and no German victim.

Why It Matters

There are two exposures here. Your own WordPress site can host the lure without you noticing, and your staff’s search for a contract or template can bring the loader into your network. Law firms and tax advisors fit the described targeting; Assumption: any Mittelstand company with an unmaintained WordPress site and weak admin protection can end up on the hosting side. The $28 million is the FBI’s figure for infrastructure as of October 2026; the FLASH gives no victim breakdown.

Patching alone does not close this. The FLASH stresses stolen credentials, unused plugins and weak admin access, and it says that deleting the downloaded file does not restore trust in a machine that ran it. Keeping core and plugins current still matters, as in our WordPress core RCE post earlier this month, but the Gootloader chain starts from access rather than a single flaw.

What You Should Do Now

  1. Endpoints: disable Windows Script Host where no business application needs it, or control scripts with WDAC or AppLocker. Block unapproved scripts and executables in user-writable folders, and keep Defender, SmartScreen, AMSI and tamper protection on.
  2. WordPress: update core, plugins and themes automatically where feasible, and remove unused plugins, themes, accounts and staging sites. Require phishing-resistant or strong MFA for administrators and hosting access, disable XML-RPC if you do not use it, and deny PHP execution under the uploads folder.
  3. Check your own site: compare core files with the official checksums, look for posts, REST routes, must-use plugins or index files you did not create, and review Search Console for indexed legal or unrelated queries you never wrote.
  4. If someone opened a downloaded JavaScript file, disconnect that machine from the network without powering it off, change credentials from a clean device once the scope is known, collect process trees and PowerShell logs, and reimage if persistence turns up. If your site is the lure, keep a forensic copy, reset hosting, SSH, SFTP, admin, database and CDN credentials from a clean system, revoke sessions, and restore only after the cause is removed.

DIESEC Perspective

The FLASH reads like two incidents in one: a web hosting problem and an endpoint problem. Most runbooks cover only one of them. Write down who would notice if your site began serving pages you never wrote, and who would notice if an accountant opened a JavaScript file from a search result.

Not sure whether your WordPress sites and script settings leave this gap open? Contact DIESEC for a rapid WordPress exposure and script-execution review.

Sources: FBI FLASH CC-111626-MW | Cyber Security News
Published: 2026-11-20 | Category: Ransomware & Extortion | ~4 min read