The FBI has warned that Gootloader malware is spreading through poisoned Google search results and compromised WordPress websites. People searching for legal contracts, business documents and policy templates may instead download malicious JavaScript that gives criminals access to their organisation’s network.
The warning was published in a TLP CLEAR FLASH advisory on 16 November 2026. It describes an active initial access campaign linked to credential theft, movement between systems and ransomware deployment.
FBI details scale of Gootloader malware campaign
As of October 2026, the FBI had identified more than 1,000 infected WordPress websites and 216 domains controlled by the Gootloader administrator. The bureau linked the operation to more than $28 million in ransomware payments, illustrating the financial impact of infections that begin with an apparently routine web search.
Gootloader malware is an initial access framework derived from the GootKit lineage. It does not normally encrypt files itself. Instead, it establishes a foothold from which attackers can install additional tools, steal credentials, explore the network and prepare a subsequent ransomware attack.
Legal and professional searches are prominent targets
The campaign targets people searching for niche legal and business information, particularly documents associated with specific jurisdictions. These may include contract clauses, agreements and other professional templates for which there is limited competition in search results.
The FBI highlighted practising attorneys, in-house counsel, law firm partners, privacy teams and legal technology decision-makers as prominent targets. The campaign has increasingly focused on US legal professionals, although the distribution method creates risks for organisations elsewhere whose staff conduct similar searches.
Attackers obtain administrator or hosting credentials for legitimate WordPress websites. They then modify those sites so they can publish lure pages, redirect selected visitors, filter traffic or relay communications. Hidden keywords, arranged backlinks and fake forum discussions help malicious pages appear relevant to search engines.
How Gootloader malware turns searches into access
The attack starts with search engine optimisation poisoning. This technique manipulates search rankings so that a compromised website appears alongside genuine resources when someone enters a carefully targeted legal or business query.
A traffic distribution system evaluates each visitor before deciding what to display. It can consider the person’s country, IP address, referring page and browser cookies. A researcher, automated scanner and intended target may therefore receive completely different content from the same URL.
From a fake document to malicious JavaScript
A selected victim is encouraged to download what appears to be the requested document. The download is commonly a ZIP archive containing a malicious JavaScript file rather than a contract or template.
If the user opens that file, Windows Script Host can execute the code outside the browser. Observed Gootloader malware chains then use PowerShell, create scheduled tasks and store components in the Windows registry. Some later-stage code can run from memory, meaning that deleting the original ZIP or script is not enough to restore confidence in the device.
The FBI advisory describes several defence evasion techniques. These include impairing the Antimalware Scan Interface, reflective code loading, process injection and process hollowing. Attackers may also sideload a malicious DLL by placing it beside easinvoker.exe, or use a mocked Windows directory with a trailing space to disguise activity.
Credential theft and lateral movement
Once established, the attackers can perform domain discovery and extract credentials. Techniques identified by the FBI include Kerberoasting, extraction of SAM or LSA registry hives and Pass-the-Hash authentication.
Gootloader-related activity can then move across a network using Windows Remote Management and Server Message Block. WinRM traffic over TCP port 5985, SMB access and short-lived remote services may therefore be significant when they follow a suspicious browser download or PowerShell execution.
This progression explains the ransomware connection. The initial script is only the entry point, while stolen credentials and remote administration mechanisms allow a follow-on operator to reach additional systems before deploying an encryptor.
Gootloader campaign timeline and exploitation status
The tradecraft has developed over several years. From 2020 to 2021, investigators documented poisoned search results, simulated forum pages, ZIP-delivered JavaScript and execution through Windows Script Host.
Between 2022 and 2024, the operation continued using SEO poisoning alongside staging in AppData, PowerShell, scheduled tasks and registry-resident payloads. During 2025 and 2026, operators added geographic filtering, abused WordPress comment paths and placed greater emphasis on US legal professionals.
New delivery methods observed in 2026 included malformed multi-part ZIP archives. These adaptations can complicate automated inspection while preserving the core social engineering technique of presenting malicious code as a useful document.
The US Department of Justice announced a disruption of infrastructure associated with Gootloader on 12 November 2026. Wider multinational action was reported on 12 and 13 November, but figures covering servers and domains across several malware families are not directly comparable with the FBI’s Gootloader-specific counts.
The FBI issued its advisory after that disruption, on 16 November 2026. Organisations should therefore not assume the law enforcement action removed the threat. The documented compromise routes remain usable, and infected WordPress sites or previously accessed Windows endpoints may still require investigation.
Affected WordPress and Windows environments
This is an active malware campaign rather than a vulnerability assigned to one product version. WordPress sites are affected when attackers obtain administrative or hosting access, exploit weak controls, or abuse exposed components. Observed intrusion points include xmlrpc.php, REST routes, injected posts, modified JavaScript and malicious must-use plugins.
Defenders should examine unexpected admin-ajax actions, including admin-ajax.php?action=ajjs_run, and unfamiliar plugins such as platformist-quadendpointer. These artefacts are investigative leads rather than proof of compromise on their own.
Windows endpoints are exposed where users can launch JavaScript through Windows Script Host and PowerShell is available for follow-on execution. Useful telemetry includes PowerShell event IDs 4103 and 4104, security events 4624, 4648, 4688, 4697, 4769, 5140, 5145 and 7045, plus relevant Sysmon process, network, image load, registry and DNS events.
The domain bashupload.com was identified as an alternate exfiltration route. Investigators should correlate any contact with this domain against script execution, credential access, service creation and lateral movement rather than treating an isolated connection as conclusive.
Actions organisations should take now
UK businesses using WordPress and Windows should concentrate on controls that interrupt this specific infection chain. Priority measures include:
- Disable Windows Script Host where it is not required, or control scripts with Windows Defender Application Control or AppLocker.
- Block unapproved scripts from downloads and other user-writable directories, while keeping Defender, SmartScreen, AMSI, cloud protection and tamper protection enabled.
- Centralise PowerShell, Windows Security, Sysmon or EDR, DNS, proxy and firewall logs so activity can be traced from download to persistence and lateral movement.
- Patch WordPress core, themes and plugins, remove unused components, restrict XML-RPC where practical and require phishing-resistant MFA for administrator and hosting accounts.
- Deny PHP execution within wp-content/uploads, monitor core and plugin integrity, and alert on unexpected REST endpoints, posts, scripts and must-use plugins.
If Gootloader malware is suspected, isolate the endpoint and preserve forensic evidence before removing files. Affected WordPress operators should retain copies of modified content, review hosting access, reset all relevant credentials and investigate whether the compromised site was used to infect visitors.
Originally reported by cybersecuritynews.com.








