A 3,200-lawyer firm just told Reuters an unauthorized actor posted a “limited” set of documents online and that firm systems were not compromised. Vermont was told Social Security numbers were in the mix.
There is a sentence American law firms have standardized, and Greenberg Traurig used the current draft. An unauthorized actor accessed a limited number of documents. Those documents appeared on the dark web. A small number of clients have been notified. Firm systems were not compromised or breached. Operations continue without disruption.
That paragraph is doing a lot of work. It is designed to sound like a near-miss. It is not a near-miss. If a client’s file, or a Social Security number sitting inside that file, is sitting on a leak site, the confidentiality duty has already failed. Calling the network “uncompromised” is a forensic distinction. The client does not live in the forensic distinction. The client lives in the PDF that other people can now download.
Reuters published the firm’s account on September 10. Greenberg Traurig, the Miami-founded giant with more than 3,200 lawyers, said it had told the affected clients directly. The same week it filed a notice with the Vermont attorney general stating that Social Security information was exposed. That notice is the part of the story that should end the “limited documents” shrug. Identity data does not become less useful to a thief because the firm counted the files on one hand.
“Limited” is the most expensive adjective in professional services
Holland & Knight and Katten used cousins of the same language in the same cycle. Attackers obtained a limited number of files. A very small number contained client information. Wider systems remained operational. All three firms said they contacted law enforcement. Cyber-intelligence sites attributed the wave to Silent Ransom Group, the crew the FBI warned in May was actively hunting U.S. law firms. The method is not cinematic. Operators pose as IT support, talk a lawyer or a staffer into a remote session, grab what they can reach, and threaten to publish if nobody pays.
That is not a nation-state campaign against a hardened enclave. That is social engineering against a business that stores other people’s worst Tuesday in searchable folders. Privilege, deal rooms, HR files, immigration packets, investigation memos, and the personal data of people who never hired the firm but appear in the matter — opposing parties, employees, witnesses, family members. A law firm is a concentration of sensitive data that did not consent to be a concentration of sensitive data. It is a processor with a professional halo.
BakerHostetler’s incident-response shop said the quiet part in a number. Its teams handled nearly 60 law-firm cybersecurity incidents in 2025, almost double the 2024 caseload. Phishing still accounts for a thick slice of the broader 1,250-plus incidents in that firm’s 2026 report. Taft Stettinius & Hollister disclosed unusual activity this March that exposed client Social Security numbers. Eckert Seamans disclosed a breach last week and drew two proposed class actions in the Southern District of New York by Wednesday. WilmerHale has been in the lawsuit pile too. Quinn Emanuel has had to talk about a compromised account. The pattern is no longer a scoop. It is a practice area.
Greenberg Traurig is not a random victim in that pattern. Google-tracked phishing infrastructure earlier this year built traps aimed at employees across private equity, ratings firms, and law firms, Greenberg Traurig among them. In August the firm told Reuters it did not have a data breach given the layers of security protocols it had in place. Weeks later it is notifying clients and Vermont. Both statements can be internally consistent if you define “breach” as “domain controller melted.” That definition is how firms lose the room.
Privilege does not survive a leak site
The legal industry still talks about these incidents as if the main risk is embarrassment. The main risk is the file. Attorney-client privilege and work product are not encryption. They are rules of evidence. They do not bind a stranger who bought access to a dump. A court can keep treating a sealed exhibit as sealed for filing purposes. It cannot unspread a document that is already listed on a criminal marketplace.
That is why the ethics problem is sharper than the tort problem. Model Rule 1.6 does not contain a footnote that says confidentiality is satisfied if the firm’s SIEM looks clean. You have a duty to take reasonable measures to prevent unauthorized disclosure. You have a duty to notify the client when disclosure happens. You have a duty not to pretend the disclosure is smaller than the client will discover when a reporter, a regulator, or a plaintiff’s firm reads the Vermont letter. “Small number of affected clients” is a notification fact. It is not a measure of harm. One matter can contain a thousand data subjects who never signed an engagement letter.
State breach statutes care about those people. Vermont did. Other AGs will if the dump is wider than the first count. HIPAA cares if the matter was health-adjacent. Securities clients care if the document is material nonpublic information sitting next to a ransom note. Banks care if the firm was a vendor in their third-party inventory. The professional-liability tower cares about all of it, usually after the first class-action complaint explains the facts more clearly than the press statement did.
Eckert Seamans is already in that second inning. Greenberg Traurig is still in the statement inning. The sequence does not usually stop at the statement.
The attacker picked the industry on purpose
Silent Ransom Group and its peers like law firms for three boring reasons. The data is dense. The victims pay, or used to pay, because the alternative is a privileged memo on a leak blog. The humans answer the phone. A partner who will not click a generic invoice will still let “IT” into a laptop when a trial starts Monday. Help-desk impersonation works in any white-collar shop. It works better in a culture that treats availability as a moral duty and security friction as a cost center.
Law-firm security programs have improved. MFA is no longer exotic. Clients put questionnaires in the RFP. Some firms finally treat a laptop like a regulated device instead of a tote bag. The incident reports say that is not the layer that is failing first. The layer that is failing is the human session that bypasses the layer. If an attacker never needs the firm’s “systems” because a lawyer handed them a remote desktop, the firm can say the systems were not breached and still be telling a kind of truth. It is the kind of truth that makes privacy counsel want to throw the engagement letter across the room.
There is also a vendor problem the statements never mention. A “limited number of documents” can leave through a collaboration portal, an e-discovery host, a copier fleet, or a contract attorney’s personal Dropbox. Saying the firm network was clean does not answer whether the document left through a processor the firm does not want to name. Clients should ask that question in writing. So should the Vermont office.
If Greenberg Traurig, or any other firm on this list, holds your matters, do not accept “limited” as the scoping memo. Ask which systems, which custodians, which date range, which document types, whether identity data beyond the Vermont SSN category is in the set, whether the actor had email, and whether any outside platform was in the path. Ask whether the firm is offering credit monitoring because it is legally required or because the dump includes the kind of data that makes credit monitoring a press-release product rather than a remedy. Ask who is paying for the client’s own forensic review. Privilege belongs to the client. The incident file should not be a black box the firm narrates.
If you run a firm, retire the sentence that says systems were not compromised when documents are on the dark web. Say what left, how it left, who was told, and what you changed so the help-desk call fails next time. Put a rule on remote-support tools that does not depend on a partner’s good mood. Segment matter data so a single session cannot vacuum a practice group. Log the hell out of file access. Monitor leak sites like they are a second docket. Notify on the statutory clock, not the reputational clock.
If you advise companies that use outside counsel, treat the firm as a vendor with a higher blast radius than your SaaS stack. Put incident timelines, subprocessors, and encryption-at-rest answers in the outside-counsel guidelines and mean them. The company that would never tolerate a processor saying “a limited number of files, but our systems are fine” should not tolerate it from the people who drafted the processor contract.
The legal market will keep calling these events anomalies until the double in BakerHostetler’s caseload becomes a triple. Silent Ransom Group will keep calling the help desk. Vermont will keep getting letters. Somewhere a client will learn their Social Security number made the trip from a matter folder to a forum they will never visit, and they will be told the firm itself was not breached. That sentence should not survive another cycle.