DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed19 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 19 filings

Orrick, Herrington & Sutcliffe LLP — February 2023 breach

Clustered 19 filings across 9 jurisdictions · filing window Jun 30, 2023 → Sep 7, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

19 filings

States

9

Affected · reported

506,475

First → last filing

Jun 30, 2023 → Sep 7, 2023

Merge confidence

100%

incident inc_b92332724170455c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 19 regulatory filings. The filings describe unauthorized access. Intrusion Feb 28, 2023–Mar 13, 2023, discovered Mar 13, 2023 — the first regulatory filing landed 109 days later (flagged late). 506,475 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 5 more. Notifications rolled out on a 69-day schedule across 19 filings beginning Jun 30, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
109days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
69days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dOregon✗ OR AG >45dMaine✗ ME AG >90d · 129dCalifornia✗ CA 60-day late · 80dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 28, 2023breach begins
Mar 13, 2023discovered
notification delay · 109 days
Jun 30, 2023first filing
Sep 7, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUN 30HHS OCRHHS OCR noticefirst filing · states nationwide total 342,176day 0
  2. JUN 30WA AGWA AG notice6,376 WA residentsday 0
  3. JUN 30MA AGMA AG notice14,325 MA residentsday 0
  4. JUN 30CA AGCA AG noticeno count statedday 0
  5. JUN 30OR AGOR AG noticestates nationwide total 118,965day 0
  6. JUL 3NH AGNH AG notice770 NH residents+3d
  7. JUL 14MT AGMT AG notice417 MT residents+14d
  8. JUL 20CA AGCA AG noticeno count stated+20d
  9. JUL 20ME AGME AG noticestates nationwide total 152,818+20d
  10. JUL 20ME AGME AG notice27 affected+20d
  11. JUL 20IN AGIN AG noticestates nationwide total 506,475+20d
  12. JUL 31CA AGCA AG noticeno count stated+31d
  13. AUG 14CA AGCA AG noticeno count stated+45d
  14. AUG 18OR AGOR AG noticestates nationwide total 461,100+49d
  15. AUG 18ME AGME AG noticestates nationwide total 461,100+49d
  16. AUG 18CA AGCA AG noticeno count stated+49d
  17. AUG 21NH AGNH AG notice449 NH residents+52d
  18. AUG 21CA AGCA AG noticeno count stated+52d
  19. SEP 7SC AGSC AG noticemost recent · 2,297 SC residents+69d
  20. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 28, 2023 – Mar 13, 2023
WA AG
Discovered
Mar 13, 2023· 13d undetected
WA AG + OR AG + NH AG +4
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
HHS OCR + WA AG + CA AG +5
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

506,475

Sum of filed state slices

39,681· 7.8% of stated

92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US506,475
IN15,275
MA14,325
WA6,376
SC2,297
NH770
MT417
ME221

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing19 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

69 days

Cadence

~1 / 3.8d

vs. multi-state median

8.6× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.