White & Case
A law firm's name on a leak site, with no evidence attached and no way to ignore it.
What happened?
The Qilin ransomware group listed White & Case, the international law firm, on its leak site on 25 October 2026.
The listing contained no proof files, no screenshots, no data samples and no other material that would demonstrate access to the firm's systems. It provided no technical description of an attack and no timeline for when an alleged intrusion might have occurred. As of 25 October, no public statement from White & Case addressing the allegation had been identified, and no independent confirmation from security media, law enforcement or a regulator was available. This entry covers a claim, not a confirmed breach.
What data was actually inside?
Nothing has been established. No data types have been disclosed, no sample has been published, and the claim itself is unverified.
What can be said is structural rather than evidentiary. An international law firm holds material that is unusual in its concentration: privileged client communications, transaction documents for deals that have not been announced, litigation strategy, investigation files, and the personal data of clients and their employees. That is a description of the sector, not of this incident, and nothing in the available reporting indicates any of it was accessed.
Who gets hurt and how?
If a claim of this kind proves accurate, the people exposed are mostly not the firm's employees. They are the firm's clients, and the clients' counterparties, and individuals named in matters who have no relationship with the firm at all.
That is the particular shape of legal sector risk. A person can be inside a law firm's files because they were a witness, an acquisition target's employee, or a party to a dispute. They never engaged the firm, cannot discover that their information is held, and have no mechanism to ask.
Unverified claims also cause real harm before anything is proven. Counsel must assess whether privilege is implicated, clients ask questions the firm cannot yet answer, and the allegation itself becomes a matter requiring response.
What did they think they were doing right?
This question cannot be answered responsibly here, because no intrusion has been confirmed and there is no identified control to examine. Inventing a failure would violate the rule this series runs on.
What is worth examining instead is the assumption the legal sector makes generally: that confidentiality obligations and the professional duty of care produce data security as a byproduct. Privilege is a legal status. It governs what may be compelled in a proceeding. It has no effect on what can be copied from a file server.
What did they not know about their own data?
The honest answer is that nobody outside the firm knows, and that is the point worth drawing out.
When an unverified listing appears, the organisation's first task is not remediation. It is determining whether the claim is true, which means establishing what exists, where it sits, and whether any of it moved. A firm that already maintains that picture can assess the allegation in hours and say something credible. A firm that does not must build the picture under time pressure while clients are asking.
The claim being unsubstantiated does not remove that work. It is the same work either way, and the only variable is whether it was done beforehand. This is the cheapest lesson in the series, because it costs nothing to learn from an incident that may not have happened.
If your environment was compromised today, could you say within 24 hours exactly what sensitive data was accessed?
Not sure where to start? How to find sensitive data across your estate
What does attribution look like the morning after?
Qilin has been among the more active operators in 2026 by published victim count. Leak site listings are a negotiating instrument as much as a disclosure, and a listing without proof is consistent with several explanations: an intrusion the group has not yet substantiated, an exaggeration, a third party compromise being attributed to a recognisable name, or a fabrication.
For the firm, the obligations do not wait for that to resolve. If client data is implicated, notification duties arise under the regimes covering each client relationship, and professional conduct rules add their own. The determining question is again the field list. The Greenberg Traurig entry in this series covers a confirmed incident at another large firm.
What would have changed the outcome?
For an allegation, the thing that changes the outcome is the ability to answer it quickly and accurately. That capability is an inventory: which matters hold personal data, which systems hold privileged material, and what left the environment.
A firm that can say what exists and demonstrate that nothing moved resolves a false claim in a news cycle. A firm that cannot spends weeks unable to confirm or deny, which produces much of the reputational damage a real breach would have caused.
White & Case found out the hard way.
Your team could spend the next 6 months rebuilding systems, notifying customers, and answering legal questions. Or you could spend 24 hours finding out what's actually at risk.
Want to understand the process first? Read our guide to sensitive data discovery .