What happened
On 16 November 2026, the FBI released FLASH CC-111626-MW on Gootloader’s SEO-poisoning and compromised-website access chain. The FBI says it observed the campaign between 2020 and 2026 and, as of October 2026, had identified more than 1,000 infected WordPress sites and 216 administrator-controlled domains linked to more than $28 million in ransomware payments. The FBI says Gootloader search terms targeted practising attorneys, in-house counsel, law-firm partners, litigation and privacy teams, legal operations, general counsel and legal-technology decision-makers.
On 12 November 2026, the Justice Department announced removal of Gootloader from more than 100 servers and said the malware had infected at least 25,000 computers since 2018. The Justice Department tied Gootloader to ransomware attacks against at least 44 United States victims and approximately $28.8 million in losses. The disruption covered identified infrastructure, but the FBI’s later FLASH focuses on the wider delivery, execution, credential and lateral-movement chain that enterprises still need to investigate.
The FBI’s detection table names PowerShell events 4103 and 4104, Windows Security events 4624, 4648, 4688, 4697, 4769, 5140 and 5145, and Sysmon events 1, 3, 7, 8, 10, 11, 13 and 22. The FBI advises defenders to monitor xmlrpc.php, disable Windows Script Host where unnecessary, and preserve endpoint memory, process trees, scheduled tasks, browser history, DNS, proxy and PowerShell logs after a JavaScript file is opened. The cited FBI FLASH did not publish a single CVE or affected WordPress version range. Attribution posture: The FBI and Justice Department did not identify a named Gootloader operator in the cited documents.
Why this matters now
The FBI warning changes the posture after the earlier law-enforcement disruption. Infrastructure removal reduced part of the criminal service, but the FLASH documents a campaign model built on compromised websites, search manipulation, traffic filtering, script execution and valid credentials. Defenders cannot treat a server takedown as proof that poisoned pages, downloaded archives or previously infected endpoints have disappeared.
Legal professionals are unusually exposed because their work requires searching for narrow jurisdiction-specific clauses, forms and precedents. The lure may therefore appear in a normal work process and bypass controls focused on unsolicited email. Law firms also hold privileged client material, while in-house counsel often have broad access to transactions, investigations, contracts and executive communications.
The campaign creates two simultaneous enterprise hunts. Web teams must determine whether owned or agency-managed WordPress sites were converted into lure or relay infrastructure. Endpoint and identity teams must identify users who downloaded or opened JavaScript archives and then test for PowerShell execution, persistence, credential exposure and lateral movement.
The decision for security leaders
Assign one coordinated hunt across browser, endpoint, identity and web-hosting evidence. The search query and download establish initial exposure; script, process and memory evidence determine execution; identity and lateral-movement telemetry determine whether the event became an intrusion. A clean antivirus scan or deleted archive is not sufficient closure.
Give legal operations a role in prevention and reporting. Users should know that a search result for a credible legal phrase can be the lure, and the help route must preserve the query, URL, filename and browser history rather than instructing immediate deletion. This is a business-workflow control, not only a security-awareness message.
Treat compromised WordPress infrastructure as a possible enterprise incident even when it hosts marketing content. Unexpected posts, new REST routes, modified JavaScript, administrator access and XML-RPC activity can make the organisation an unwitting malware distributor, creating customer, reputation and law-enforcement consequences beyond website availability.
Evidence of closure
- Correlated hunt results covering browser downloads, PowerShell, identity and lateral-movement telemetry.
- Forensic disposition for every endpoint that opened a suspicious JavaScript file.
- Validated WordPress integrity comparison covering core, plugins, themes, posts, REST routes and JavaScript.
- Documented credential scope and rotation evidence from a known-clean administrative path.
The Security.io assessment
The FBI and Justice Department provide high-confidence evidence of campaign scale, ransomware linkage and disruption activity. The figures are aggregate and historical; they do not establish how many delivery sites or infected endpoints remained active at publication. The campaign should therefore be hunted from behaviour and user activity rather than from an assumption that every identified domain remains current.
The authoritative warning does not reduce the problem to a WordPress patch. The FBI describes compromised credentials, vulnerable plugins and themes, XML-RPC, REST routes and modified JavaScript, without naming one CVE or version boundary. Exposure management must therefore include account security, file integrity, hosted-site ownership and logging, particularly for sites operated by agencies or separate business units.
The strongest escalation signal is not merely a downloaded archive. Opening the JavaScript file, followed by encoded PowerShell, AMSI interference, persistence, credential activity or remote administration, should move the case into full incident response. That distinction prevents both underreaction to real execution and unnecessary enterprise-wide escalation for preserved but unopened files.
Questions for the morning meeting
- Have legal and privacy teams been briefed that specialised document searches can be an initial-access route?
- Can the SOC correlate browser downloads with PowerShell, WinRM, WMI and SMB activity?
- Which externally managed WordPress sites can change JavaScript or create REST routes without central detection?
- Does endpoint recovery require reimaging after confirmed follow-on malware or persistence?