Clustered 2 filings across 2 jurisdictions · filing window Nov 17, 2023 → Nov 20, 2023. View entity profile → Other incidents for this victim →
incident inc_201fd9c864e3466a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA WA
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.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 30, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 26, 2023
Reported by CALIFORNIA AG filing
Sep 15, 2023
Reported by WASHINGTON AG filing
International Paper Company, a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2023-09-15 and filed notice on 2023-11-17. 1,057 Washington residents were affected. 63 days elapsed between awareness and notification. 108 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 1,057
International Paper Company notified the California AG of a data breach affecting its Group Health and Welfare Plan participants. The incident occurred on May 30, 2023, when an unauthorized actor exploited a vulnerability in Progress Software's MOVEit Transfer tool used by third-party vendor Welltok, Inc. Welltok discovered the potential impact on July 26, 2023, and confirmed data exfiltration. Affected data includes personal information and electronic protected health information (ePHI). Welltok is offering 24 months of credit monitoring via Experian.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.