Case Library / ClickFix & SEO Poisoning / GootLoader and SocGholish Dual Campaign Against Six Law Firms (2023)

GootLoader and SocGholish Dual Campaign Against Six Law Firms (2023)

eSentire's Threat Response Unit blocked 10 separate attacks across six unnamed law firms in Jan-Feb 2023, foiling two parallel campaigns: SEO-poisoned fake "agreement" downloads delivering GootLoader, and a compromised Notary Public website serving a fake Chrome update to deliver SocGholish.

Share:

Reviewed by the Social Engineering Examples team.

What Happened

Between January and February 2023, eSentire's Threat Response Unit (TRU) identified and blocked 10 separate cyberattacks against employees at six different, unnamed law firms. The activity came from two unrelated malware campaigns running concurrently: one delivering GootLoader via black-hat SEO poisoning of compromised WordPress sites carrying fake "legal agreement" content, and the other delivering SocGholish (FakeUpdates) via a watering-hole compromise of a Notary Public website in the Miami area that legal professionals commonly visited, which served a fake Chrome browser-update prompt. eSentire published its findings on February 28, 2023, noting that unlike prior GootLoader campaigns it had tracked (which led to SunCrypt/REvil ransomware or Cobalt Strike), the January-February 2023 law-firm-targeted GootLoader activity did not result in ransomware deployment, which TRU flagged as a possible shift toward espionage or data-exfiltration motives.

How the Attack Worked

Two independent, technically distinct infection chains ran in parallel against the same target vertical (law firm employees). GootLoader chain: attackers used black-hat SEO poisoning to get legitimate but compromised WordPress sites (hacked without the site owners' knowledge) to rank highly for niche legal search terms such as "agreement," "contract," or "contract salary calculator," phrases with low SEO competition that let a single poisoned blog post climb into the top five search results. An employee searching for a template would click through to what looked like an online forum thread answering their exact question, which hosted a ZIP archive purporting to be the requested agreement or contract template. Inside the ZIP was a malicious JavaScript (.js) file; when the victim double-clicked it expecting a document, it silently executed GootLoader, which established persistence and (per eSentire's related case research) has been used to drop Cobalt Strike into memory and enable hands-on-keyboard access within roughly two hours in similar intrusions. SocGholish/FakeUpdates chain: attackers compromised a legitimate Notary Public website in the Miami area that legal professionals routinely visited for notarization needs, and injected code that displayed a convincing fake "Chrome browser update is required" overlay. A visitor who clicked to accept the update instead downloaded SocGholish, a JavaScript-based loader that (in the broader threat landscape) commonly stages Cobalt Strike and has been paired with ransomware such as LockBit in other incidents, though no such follow-on was reported in this eSentire case set.

The Lure & the Tell

The lure worked because it hijacked two forms of implicit trust legal professionals rely on daily: trust in search engine rankings (a top-five Google result for "contract salary calculator" or "agreement template" felt authoritative) and trust in a routine, already-bookmarked professional resource (a Notary Public site legal staff visited normally). The GootLoader "tell" was subtle: the destination page mimicked an online forum rather than a proper legal-document repository, and the "document" delivered was a .js script inside a ZIP rather than a .docx/.pdf. The SocGholish "tell" was that a genuine Chrome update never originates from a website's own content or overlay, since it comes from the browser itself (chrome://settings/help), but the fake prompt was styled convincingly enough to pass casual inspection, especially for non-technical legal staff.

Outcome

All 10 attack attempts against the six law firms were detected and blocked by eSentire before completing their objective; eSentire reported no confirmed breach, data theft, or ransomware deployment tied to this specific incident set. eSentire's analysts noted that despite GootLoader's known capability (in 2022 and other campaigns) to lead to SunCrypt/REvil ransomware or Cobalt Strike, the January-February 2023 law-firm-targeted GootLoader activity notably did not deploy ransomware, which the TRU team assessed as a possible indicator the campaign had shifted toward espionage/data-exfiltration objectives rather than purely financially-motivated extortion.

Why It Matters

This case is a clean, well-documented example of two of the most prevalent "living off the land"/social-engineering-adjacent delivery vectors, SEO poisoning and fake browser-update watering holes, being used together against a single high-value vertical (law firms handle sensitive client, M&A, and litigation data, making them attractive espionage and extortion targets). It illustrates that initial-access brokers don't need phishing emails at all: abusing search-engine trust and a routinely-visited legitimate third-party site was enough to reach the intended victims. It also demonstrates why "was this a legitimate browser update or search result" needs to be part of end-user security training for professional-services staff, and shows a security vendor's real detection-and-block outcome (rather than a breach post-mortem), useful for illustrating that these techniques are common enough to appear as routine SOC blocks across multiple same-industry clients in a two-month window.

Defenses

eSentire's Threat Response Unit (TRU) and MDR/SOC detected and blocked all 10 attempts before execution completed, isolating hosts and blocklisting C2 infrastructure (per related Jan 12, 2023 GootLoader case study). General defenses that would mitigate this vector: web-filtering/DNS blocking of newly-registered or reputation-poor domains, blocking JavaScript (.js) execution via double-click from downloaded ZIP archives (associate .js with a text editor, not wscript/cscript), disabling or tightly controlling browser "update" prompts that originate from page content rather than the browser itself, EDR rules flagging wscript.exe/mshta.exe spawned from browser downloads, user training that legitimate browser updates never come from a website pop-up, and monitoring for anomalous outbound beaconing consistent with Cobalt Strike staging. Because GootLoader operators are known to also deliver ransomware (SunCrypt, REvil/Sodinokibi) and Cobalt Strike in other campaigns, rapid detection-to-containment (eSentire cited ~2 hours in a related case) was the decisive control here.

Sources
Attack Chain & Defense
The sequence the attacker ran
How it could have been stopped
1
Reconnaissance and keyword/target research: GootLoader operators are documented (per eSentire) as selecting niche legal phrases such as "agreement" or "contract salary calculator" with little SEO competition, and SocGholish/TA569-style operators typically scan the web at scale for vulnerable, legitimate WordPress sites (including ones with above-average or specialized traffic, such as a Notary Public site frequented by legal firms) worth compromising as watering holes.
Countering Stage 1: Which specific low-competition search phrases or which third-party sites an attacker will target is largely unpredictable and outside a law firm's control; the realistic control is assuming this reconnaissance happens and hardening the moments downstream where an employee actually encounters the resulting lure.
2
Third-party infrastructure compromise: Attackers compromised legitimate but vulnerable WordPress websites, likely via known CMS/plugin vulnerabilities or weak credentials, without the site owners' knowledge, gaining the ability to add blog content (GootLoader) or inject page overlays (SocGholish).
Countering Stage 2: Third-party website compromise (a Notary Public's site, an unrelated WordPress blog) is not something a law firm can patch or monitor directly; web-filtering and DNS reputation services that flag newly-registered or reputation-poor domains before an employee's browser loads them is the nearest practical control.
3
Decoy and payload staging: GootLoader operators authored blog posts formatted to look like an online forum thread answering the target's exact search query, hosting a ZIP archive containing a malicious JavaScript file disguised as a contract or agreement template; SocGholish operators injected a fake "Chrome browser update required" overlay onto the compromised site.
Countering Stage 3: Security-awareness training that teaches staff to notice mismatches, a forum page instead of a proper legal-document site, a downloaded .js file instead of the expected .docx or .pdf, gives employees a chance to catch the decoy before opening it.
4
Search-result poisoning: Black-hat SEO techniques pushed the GootLoader-laced blog posts into the top five search results for the targeted legal phrases, so that a law firm employee's normal search led straight to the poisoned page.
Countering Stage 4: The same web-filtering/DNS-reputation controls from Stage 2 apply here, since a poisoned search result only becomes dangerous once the browser is allowed to load the underlying compromised domain.
5
Victim engagement: A law firm employee searching for a document template clicked through to the poisoned forum page (GootLoader), or a legal professional visited the routinely-trusted Notary Public site and was met with the fake browser-update prompt (SocGholish).
Countering Stage 5: User training that legitimate browser updates never originate from a website's own content or overlay, only from the browser's own settings menu, and that legal document templates should come from a trusted internal repository rather than a search-engine result, directly targets this decision point.
6
Malicious execution: The employee downloaded and double-clicked the ZIP/.js file expecting a document (GootLoader), or clicked to accept the fake Chrome update (SocGholish), silently executing the loader in either case.
Countering Stage 6: Technical controls that block JavaScript (.js) from executing on double-click (associating .js with a text editor rather than wscript/cscript), plus Windows Attack Surface Reduction rules blocking JScript/VBScript from launching downloaded content, stop the loader from ever running even if the file is opened.
7
Persistence and initial foothold: The loader established persistence on the host, consistent with eSentire's related case findings of scheduled tasks and disguised file names used to survive reboots and evade casual inspection.
Countering Stage 7: EDR rules flagging unusual scheduled-task creation or registry Run-key persistence tied to a file that originated from a browser download let a SOC catch the infection before it is used for anything further.
8
Escalation to hands-on-keyboard access: Per eSentire's related January 2023 case study, GootLoader intrusions have progressed to a human operator deploying Cobalt Strike, running credential-harvesting and Active-Directory reconnaissance tooling, and attempting lateral movement within roughly two hours of initial infection; SocGholish is documented industry-wide as commonly staging Cobalt Strike in the same way.
Countering Stage 8: 24/7 MDR/SOC monitoring for Cobalt Strike beaconing and anomalous PowerShell activity (eSentire cited its own machine-learning PowerShell classifier catching this pattern), paired with rapid host isolation, is the control that stopped escalation from turning into a full intrusion in eSentire's related case.
9
Objective completion (blocked in this case): The end goal in comparable intrusions is data theft, espionage collection, or handoff to a ransomware affiliate; in this specific 10-attack, six-law-firm case set, eSentire's SOC detected and isolated every affected host and blocklisted the command-and-control infrastructure before any attacker reached this stage.
Countering Stage 9: Rapid detection-to-containment, eSentire isolating hosts and blocklisting command-and-control infrastructure typically within a couple of hours of initial infection in comparable cases, was the decisive control that kept all 10 of these attempts from reaching a completed objective.
Quick Facts
Victim
Six unnamed law firms (client identities withheld by eSentire)
Location
United States (Notary Public watering-hole site geolocated to the Miami, Florida area); six unnamed law firms, locations not disclosed
Date
2023-01 to 2023-02 (attacks); report published 2023-02-28
Impact
No financial loss, ransom payment, or breach was disclosed. eSentire reported all 10 attack attempts were blocked before completion; no confirmed data exfiltration, ransomware deployment, or business email compromise was reported for this specific six-law-firm incident set.
Status
Confirmed
Case Type
Real-World Incident
Sector
Legal Services
Threat Actor
Organized Crime
Related

Related Cases

Gootloader Returns After 7-Month Hiatus: SEO Poisoning, Glyph-Swapped Fonts, and a Dual-Personality Malformed ZIP (2025)

After going quiet on March 31, 2025 following a researcher's disruption campaign, Gootloader returned on November 5, 2025 with a…

Incident 2025Read →

UAC-0050 ClickFix Fake-reCAPTCHA Campaign Deploys 'Lucky Volunteer' Infostealer Against Ukrainian Organizations

A Ukrainian-language "shared document" phishing wave used a fake reCAPTCHA "verify you are human" ClickFix page to trick victims into…

Incident 2024Read →

Lampion Banking Trojan ClickFix Campaign vs Portuguese Government, Finance and Transport Sectors

A revived Lampion banking-trojan campaign spoofed Portugal's tax authority site to trick victims into pasting a PowerShell command into the…

Incident 2025Read →