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

INTERNATIONAL PAPER COMPANY — May 2023 breach

Clustered 6 filings across 6 jurisdictions · filing window Nov 14, 2023 → Dec 4, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

78,692

First → last filing

Nov 14, 2023 → Dec 4, 2023

Merge confidence

100%

incident inc_201fd9c864e3466a · merged by deterministic · confidence 100%

Part of the Welltok supply-chain incident (2023) — at least 6 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe hacking. Intrusion May 30, 2023–Jul 28, 2023, discovered May 31, 2023 — the first regulatory filing landed 167 days later; 1 later filing was flagged late. 78,692 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 3 more. Notifications rolled out on a 20-day schedule across 6 filings beginning Nov 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
167days

Discovered → first regulatory filing

Discovery variance
56days

Range of discovered_at dates across filings

Filing span
20days

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 clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 167 days
Nov 14, 2023first filing
Dec 4, 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. NOV 14HHS OCRHHS OCR noticefirst filing · states nationwide total 78,692day 0
  2. NOV 17WA AGWA AG notice1,057 WA residents+3d
  3. NOV 20CA AGCA AG noticeno count stated+6d
  4. NOV 22SC AGSC AG notice3,123 SC residents+8d
  5. NOV 29MA AGMA AG notice34 MA residents+15d
  6. DEC 4OR AGOR AG noticemost recent · no count stated+20d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
WA AG
Discovered
May 31, 2023OR AGJul 26, 2023WA AG + CA AG + SC AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + CA AG +2
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)

78,692

Sum of filed state slices

4,214· 5.4% of stated

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

US78,692
SC3,123
WA1,057
MA34

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 filing6 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

20 days

Cadence

~1 / 4d

vs. multi-state median

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