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

Confirmed10 filings · 9 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 10 filings

AFNI, INC. — June 2021 breach

Clustered 10 filings across 9 jurisdictions · filing window Jan 1, 2022 → Jul 12, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

261,449

First → last filing

Jan 1, 2022 → Jul 12, 2022

Merge confidence

100%

incident inc_91a7dec3d5964bd8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Jun 7, 2021, discovered Jun 7, 2021 — the first regulatory filing landed 208 days later (flagged late). 261,449 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 192-day schedule across 10 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

208days

Discovered → first regulatory filing

Discovery variance

365days

Range of discovered_at dates across filings

Filing span

192days

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 clocksCalifornia✗ CA 60-day late · 372dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 39dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 7, 2021breach begins

Jun 7, 2021discovered · members disagree

notification delay · 208 days

Jan 1, 2022first filing

Jul 12, 2022most recent filing

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

Member cascade — every filing about this breach

JAN 1IL AGIL AG noticefirst filing · no count statedday 0
JUN 2DE AGDE AG noticeno count statedauto-linked+152d
JUL 11IN AGIN AG noticestates nationwide total 261,449auto-linked+191d
JUL 11ME AGME AG noticestates nationwide total 261,449auto-linked+191d
JUL 11MA AGMA AG notice2,892 MA residentsauto-linked+191d
JUL 11CA AGCA AG noticeno count statedauto-linked+191d
JUL 11WA AGWA AG notice3,818 WA residentsauto-linked+191d
JUL 11DE AGDE AG noticeno count statedauto-linked+191d
JUL 11OR AGOR AG noticestates nationwide total 261,449auto-linked+191d
JUL 12SC AGSC AG noticemost recent · 4,443 SC residentsauto-linked+192d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 7, 2021
Discovered: Jun 7, 2021DE AG + CA AG + WA AG +1Jun 2, 2022ME AGJun 7, 2022IL AGfilings disagree on discovery
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PCI · 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)

261,449

Sum of filed state slices

14,814· 5.7% of stated

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

US261,449

SC4,443

WA3,818

IN3,399

MA2,892

ME262

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

192 days

Cadence

~1 / 21.3d

vs. multi-state median

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