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

Confirmed9 filings · 9 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 9 filings

The AFTRA Retirement Fund — October 2019 breach

Clustered 9 filings across 9 jurisdictions · filing window Feb 25, 2020 → Mar 2, 2020 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

57,900

First → last dated filing

Feb 25, 2020 → Mar 2, 2020

Merge confidence

100%

incident inc_b56d1da55abf4445 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Oct 24, 2019–Oct 28, 2019, discovered Oct 28, 2019. 57,900 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 3 more. Notifications rolled out on a 6-day schedule across 8 dated filings beginning Feb 25, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

6days

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 >45dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 24, 2019breach begins

Oct 28, 2019discovered

Feb 25, 2020first dated filing

Mar 2, 2020most 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 about this breach

JAN 1IL AGIL AG noticefiling day not on record · no count stated—
FEB 25WA AGWA AG noticefirst filing · 8,803 WA residentsauto-linkedday 0
FEB 25IN AGIN AG noticestates nationwide total 57,207auto-linkedday 0
FEB 25MA AGMA AG notice8,222 MA residentsauto-linkedday 0
FEB 25CA AGCA AG noticeno count statedauto-linkedday 0
FEB 25MT AGMT AG notice411 MT residentsauto-linkedday 0
FEB 25OR AGOR AG noticestates nationwide total 57,207auto-linkedday 0
FEB 25HHS OCRHHS OCR noticestates nationwide total 57,900auto-linkedday 0
MAR 2NH AGNH AG noticemost recent · 90 NH residentsauto-linked+6d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Oct 24, 2019 – Oct 28, 2019
Discovered: Oct 28, 2019· 4d undetected
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)

57,900

Sum of filed state slices

19,562· 33.8% of stated

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

US57,900

WA8,803

MA8,222

IN2,036

MT411

NH90

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

6 days

Cadence

~1 / 0.9d

vs. multi-state median

1.0× faster

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.