All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed10 filings · 7 statesUnverified claimConfirmedEnforcedblacksuithigh sensitivity

Merged incident · 10 filings

Octapharma Plasma, Inc. — April 2024 breach

Clustered 10 filings across 8 jurisdictions · filing window Apr 15, 2024 → Sep 20, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

271,665

First → last filing

Apr 15, 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 2 unverified claims. The filings describe unauthorized access. Intrusion Apr 17, 2024, discovered Apr 17, 2024 — the first regulatory filing landed 106 days later (flagged late). 271,665 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 158-day schedule across 7 filings beginning Apr 15, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

106days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

108days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

158days

Time between earliest and latest filing

Not recorded for this incident

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

notification delay · 106 days

Aug 1, 2024first filing

Sep 20, 2024most recent filing

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

Member cascade — every filing about this breach

APR 15Leak siteblacksuit postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
APR 23Leak siteblacksuit postattacker claim · unverifiedoperator-confirmed+9d
AUG 1IL AGIL AG noticeno count stated+108d
AUG 30IN AGIN AG noticestates nationwide total 271,665auto-linked+137d
AUG 30WA AGWA AG notice9,127 WA residentsauto-linked+137d
SEP 15OR AGOR AG noticestates nationwide total 271,665auto-linked+153d
SEP 19CA AGCA AG noticeno count statedauto-linked+157d
SEP 20SC AGSC AG notice2,114 SC residentsauto-linked+158d
SEP 20MA AGMA AG noticemost recent · 164 MA residentsauto-linked+158d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Apr 17, 2024
Discovered: Apr 17, 2024
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Unauthorized Access

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 claim2 members

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 22, 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

158 days

Cadence

~1 / 17.6d

vs. multi-state median

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