FBI Details Gootloader SEO Poisoning and WordPress Compromises

· Original article ↗

Summary

An FBI FLASH describes Gootloader’s SEO-poisoning and compromised-WordPress tactics, reporting over 1,000 infected sites and 216 actor-controlled domains. It details the malware’s evolution and recommends Windows and WordPress defenses.

Key points

  • The FBI reports that Gootloader was used for initial access and as a ransomware precursor; its activity was associated with more than $28 million in ransomware payments.
  • From 2020 to 2026, operators used SEO-poisoned searches and compromised WordPress sites to lure visitors, redirect traffic, and filter content by factors including country and referrer.
  • The FBI describes stolen credentials being used to access WordPress sites, with injected posts, modified JavaScript, and abuse of plugins, XML-RPC, and REST routes.
  • Reported techniques evolved from ZIP-delivered JavaScript and Windows Script Host execution to PowerShell, scheduled tasks, registry-resident payloads, and later geofencing and traffic distribution services.
  • The advisory identifies Windows event logs and EDR telemetry for investigating suspicious scripts, remote access, process activity, and other behaviors.
  • Recommended defenses include reducing WordPress attack surface, restricting XML-RPC, enforcing strong administrator MFA, monitoring site integrity, and retaining centralized logs.

Article Details

Attack Vectors
  • SEO poisoning placed attacker-controlled pages alongside legitimate search results for targeted legal queries, leading visitors to Gootloader lures.
  • Gootloader used ZIP-delivered JavaScript and Windows Script Host execution in 2020–2021; later activity included Trojanized JavaScript libraries and PowerShell.
  • The Gootloader administrator scanned WordPress sites for xmlrpc.php and used compromised credentials to access vulnerable plugins and themes.
  • Compromised WordPress sites served as lure pages, redirectors, traffic filters, or relay infrastructure; the administrator injected posts, XML-RPC and REST routes, and modified JavaScript.
  • A traffic distribution system filtered content by country, referrer, cookie, or IP address.
Defensive Notes
  • Keep WordPress core, trusted plugins, and themes updated; remove unused components and accounts, and use virtual patching for emergency exposure.
  • Protect WordPress administration with strong or phishing-resistant MFA, restrict hosting access, disable or rate-limit XML-RPC when appropriate, and monitor authentication and POST volume.
  • Run PHP with least privilege, prevent PHP execution under wp-content/uploads, protect wp-config.php, and alert on unexpected REST endpoints, admin-ajax actions, and file changes.
  • Disable Windows Script Host where not required or control script execution with WDAC or AppLocker; block unapproved scripts and executables from user-writable locations.
  • Preserve web, authentication, DNS, proxy, PowerShell, endpoint, and firewall evidence. If compromise is suspected, isolate affected endpoints and WordPress sites, reset credentials from a clean system, and restore only from a known-clean backup after addressing the access path.

Indicators of compromise

TypeIndicatorContext
DOMAINbashupload[.]comThe article identifies this domain as an alternate upload destination for exfiltration over cloud storage.

MITRE ATT&CK

T1021.002 · SMB/Windows Admin SharesThe article describes C$ staging and low-level SMB authentication.T1021.006 · Windows Remote ManagementThe article describes Invoke-Command and TCP 5985 discovery for Windows Remote Management.T1027 · Obfuscated Files or InformationThe article describes randomized names, string substitution, and compressed or encoded payloads.T1047 · Windows Management InstrumentationThe article describes WMI process creation and access testing.T1055 · Process InjectionThe article describes writing into another process and creating a remote thread.T1055.012 · Process HollowingThe article describes replacing a suspended process image.T1059.001 · PowerShellThe article says Gootloader payloads used PowerShell templates or commands.T1078 · Valid AccountsThe article says supplied credentials were used with WinRM, WMI, and SMB.T1140 · Deobfuscate/Decode Files or InformationThe article describes Base64, gzip, and raw-deflate decoding and runtime reconstruction of payloads.T1548.002 · Bypass User Account ControlThe article describes using a mock trusted directory and an auto-elevated executable to bypass User Account Control.T1550.002 · Pass the HashThe article describes an NTLM hash used directly for SMB authentication.T1562.001 · Disable or Modify ToolsThe article describes patching AmsiScanBuffer.T1569.002 · Service ExecutionThe article describes starting and deleting remote services.T1574.002 · DLL Side-LoadingThe article describes placing a DLL next to a copied easinvoker.exe.T1620 · Reflective Code LoadingThe article says Assembly.Load executed managed payloads without a normal on-disk assembly load.

Threat Actors

Malware

Products

Tools

Countries

Industries

Related Articles