DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 11 filings

Industrial Acceptance Corporation — February 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Feb 27, 2025 → Jun 1, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

79,216

First → last filing

Feb 27, 2025 → Jun 1, 2026

Merge confidence

100%

incident inc_123f815e368b4f74 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Feb 22, 2025–Feb 24, 2025, discovered Feb 24, 2025 — the first regulatory filing landed 431 days later (flagged late). 79,216 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 459-day schedule across 10 filings beginning Feb 27, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
431days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
428days 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
459days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 458dMaine✗ ME AG >90d · 459dTexas✗ TX AG >30dMassachusetts✗ MA AG >90dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 22, 2025breach begins
Feb 24, 2025discovered
notification delay · 431 days
May 1, 2026first filing
Jun 1, 2026most 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. FEB 27Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. MAY 1IL AGIL AG noticeno count stated+428d
  3. MAY 28IN AGIN AG noticestates nationwide total 79,216+455d
  4. MAY 28NH AGNH AG notice966 NH residents+455d
  5. MAY 28NE AGNE AG notice111 NE residents+455d
  6. MAY 28CA AGCA AG notice808 CA residents+455d
  7. MAY 29ME AGME AG noticestates nationwide total 79,216+456d
  8. MAY 29TX AGTX AG noticestates nationwide total 79,216+456d
  9. MAY 29MA AGMA AG notice7,976 MA residents+456d
  10. JUN 1WA AGWA AG notice679 WA residents+459d
  11. JUN 1VT AGVT AG noticemost recent · 40 VT residents+459d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 24, 2025
IN AG
Discovered
Feb 24, 2025
IL AG + NH AG + NE AG +5
Data types
Financial account · Identity (basic) · Government ID · PII
IL AG + MA AG + NH AG +6
Attack vector
Ransomware
NH AG

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)

79,216

Sum of filed state slices

13,846· 17.5% of stated

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

US79,216
MA7,976
TX2,706
NH966
CA808
WA679
IN334
ME226
NE111
VT40

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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

459 days

Cadence

~1 / 45.9d

vs. multi-state median

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