DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressState AGConfirmed9 records · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblacksuithigh sensitivity
Merged incident · 9 records

Octapharma Plasma, Inc. — April 2024 breach

Clustered 9 records across 7 jurisdictions: 7 filings, 1 press report and 1 leak-site claim · filing window Aug 30, 2024 → Sep 20, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 records

States

7

Affected · reported

271,665

First → last dated filing

Aug 30, 2024 → Sep 20, 2024

Merge confidence

100%

incident inc_e1408b4d00b14924 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 17, 2024, discovered Apr 17, 2024. 271,665 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 21-day schedule across 6 dated filings beginning Aug 30, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
21days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 135dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 17, 2024breach begins
Apr 17, 2024discovered
Aug 30, 2024first dated filing
Sep 20, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. APR 15Leak siteblacksuit postfirst record · attacker claim · unverifiedday 0
  2. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  3. AUG 30WA AGWA AG notice9,127 WA residents+137d
  4. AUG 30IN AGIN AG noticestates nationwide total 271,665+137d
  5. SEP 15OR AGOR AG noticestates nationwide total 271,665+153d
  6. SEP 19CA AGCA AG noticeno count stated+157d
  7. SEP 20SC AGSC AG notice2,114 SC residents+158d
  8. SEP 20MA AGMA AG noticemost recent · 164 MA residents+158d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 17, 2024
WA AG
Discovered
Apr 17, 2024
IL AG + WA AG + CA AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MA AG + CA AG +1
Attack vector
Unauthorized Access
WA AG

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)

271,665

Sum of filed state slices

16,527· 6.1% of stated

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

US271,665
WA9,127
IN5,122
SC2,114
MA164

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing7 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 Aug 9, 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

21 days

Cadence

~1 / 4.2d

vs. multi-state median

3.5× 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.