Back to BlogLegal Tech

45 Law Firm Ransomware Attacks in 2023

2023 saw a record 45 ransomware attacks on law firms, compromising 1.6M records. Learn why law firms are prime targets and how to protect client data.

February 18, 20267 minute read
law firm securityransomwarelegal data breachattorney-client privilege

Updated for 2026

A Record Year for Law Firm Attacks

2023 set a grim record: 45 ransomware attacks on law firms. That is the highest count ever logged. These attacks hit over 1.6 million records. Ransom demands averaged $2.47 million.

The legal sector has become a prime target. The threat is not slowing.

Why Law Firms Are Prime Targets

Law firms hold some of the most valuable data anywhere:

  1. Client secrets protected by attorney-client privilege
  2. Merger and deal details worth millions
  3. Court strategies rivals would pay to see
  4. Personal data of high-net-worth clients
  5. Trade secrets shared in legal cases

Attackers know firms will pay. They pay to stop both theft and public exposure.

The Financial Impact

MetricValueSource
Average breach cost$5.08MEmbroker 2024
Average ransom demand$2.47MComparitech
Firms with response plans34%ABA 2023
Firms that lost client data56%ABA Survey
Orrick settlement$8MCourt filings

A law firm data breach cost $5.08 million on average in 2024. That is a 10%+ rise from the prior year. And it only covers direct costs.

Case Study: Orrick, Herrington & Sutcliffe

In November 2024, Orrick agreed to pay $8 million. This settled class action claims from a March 2023 breach.

The breach hit 638,000+ people. Only 153,000 were first reported. Stolen data included names, addresses, dates of birth, and Social Security numbers.

The irony: Orrick helps firms that have faced security breaches.

The Redaction Problem

A top cause of data exposure is not hacking. It is improper redaction.

Many lawyers use Word's highlight tool to "redact" documents. This does not remove data. It only covers it. Recipients can:

  • Select and copy the "redacted" text
  • Remove the highlight
  • Use PDF tools to pull hidden content

Courts have fined attorneys for these errors. One judge demanded counsel explain "technical weakness" in their redaction process.

True Document Redaction: The Fix

anonym.legal's Office Add-in gives true redaction in Microsoft Word. Learn more on the security and compliance page and in the legal conformance docs.

How It Works

  1. Select text in your Word document
  2. Click "Anonymize" in the anonym.legal add-in
  3. PII is found and replaced with tokens
  4. The text is actually replaced—not just hidden
  • Reversible encryption: Keep originals with keys
  • Batch processing: Handle entire case files at once
  • Audit trails: Record what was removed and when
  • Format preservation: Document layout stays intact

Why Reversibility Matters

anonym.legal uses AES-256-GCM encryption. It can be reversed with the right key. This matters because:

  • Courts may need the original document
  • Opposing counsel may contest redactions
  • Internal review may need full text
  • Auditors may request un-redacted versions

Security Beyond Redaction

Proper redaction is key. But it is only part of the answer. Law firms also need:

AI Chat Protection — Associates use ChatGPT for research. Are they pasting client data? The token system stops that at the source.

Email Scanning — Scan for accidental PII before sending files out.

Document Classification — Know which files hold privileged data before sharing.

Getting Started

Protect your firm today:

  1. Download Office Add-in — True redaction in Word
  2. Install Chrome Extension — Guard AI usage
  3. Start free trial — 200 tokens to test

When This Approach Has Limits

True redaction and AI-paste controls reduce a law firm's exposure, but they are not a complete defense and should be planned with their limits in mind.

Redaction is one control, not the whole defense. Replacing visual highlighting with true redaction closes one common leak, but ransomware crews exfiltrate whole files — including documents that were never redacted at all. Redaction protects what you ship outward; it does not stop an intruder who already has network access from taking everything else.

Detection is probabilistic, so a privileged name can still slip through. Automated detection misses some identifiers and flags some non-identifiers, and the miss rate rises with scanned exhibits, handwriting, and unusual name formats. For privileged or court-bound material, a human reviewer still has to check the output before it leaves the firm.

Reversible protection is only as strong as key custody. Tokenization lets you restore originals when a court or auditor needs them, but anyone holding the key holds the data. If that key is stored carelessly — or sits on a machine the attacker reaches — reversible protection offers little against the breach you are trying to prevent.

Tools do not replace the duty of competence. Encryption, redaction, and paste-blocking are safeguards a firm chooses and configures; they do not discharge the attorney's professional obligation to supervise how client data is handled. Treat them as part of an incident-response and training program, not a substitute for one.


Sources

Limitations / When this doesn't apply

Redaction is one control, not the whole defense: replacing visual highlighting with true redaction closes a common leak, but ransomware crews exfiltrate entire files — including documents that were never redacted. These safeguards protect what you ship outward, not against an intruder who already has network access.

  • Automated PII detection is probabilistic, so a privileged name can still slip through — the miss rate rises with scanned exhibits, handwriting, and unusual name formats, so privileged or court-bound material still needs human review before it leaves the firm.
  • Reversible tokenization is only as strong as key custody: anyone holding the key holds the data, so a carelessly stored key undermines the protection.
  • This article is educational, not legal advice; the safeguards described do not discharge an attorney's professional duty of competence or replace an incident-response and training program.

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.