DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed13 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

Mortgage Industry Advisory Corporation — April 2023 breach

Clustered 13 filings across 6 jurisdictions · filing window May 22, 2023 → Sep 5, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

6

Affected · reported

8,973

First → last filing

May 22, 2023 → Sep 5, 2023

Merge confidence

100%

incident inc_63ab873323484e55 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Apr 5, 2023–Apr 6, 2023, discovered Apr 6, 2023 — the first regulatory filing landed 46 days later (flagged late). 8,973 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 106-day schedule across 13 filings beginning May 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
46days

Discovered → first regulatory filing

Discovery variance
138days

Range of discovered_at dates across filings

Filing span
106days

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 clocksVermont✗ VT AG >45 bdayMassachusetts⏱ MA AG >30dMaine⏱ ME AG >30d · 47dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 5, 2023breach begins
Apr 6, 2023discovered · members disagree
notification delay · 46 days
May 22, 2023first filing
Sep 5, 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. MAY 22MA AGMA AG noticefirst filing · 181 MA residentsday 0
  2. MAY 22MT AGMT AG notice54 MT residentsday 0
  3. MAY 26NH AGNH AG notice2 NH residents+4d
  4. JUN 12VT AGVT AG noticeno count stated+21d
  5. JUL 10NH AGNH AG notice2 NH residents+49d
  6. JUL 20NH AGNH AG noticeno count stated+59d
  7. JUL 25ME AGME AG noticestates nationwide total 8,973+64d
  8. JUL 31NH AGNH AG notice11 NH residents+70d
  9. SEP 1OR AGOR AG noticestates nationwide total 856+102d
  10. SEP 1ME AGME AG noticestates nationwide total 856+102d
  11. SEP 5ME AGME AG noticestates nationwide total 1,805+106d
  12. SEP 5NH AGNH AG notice7 NH residents+106d
  13. SEP 5VT AGVT AG noticemost recent · no count stated+106d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 5, 2023 – Apr 6, 2023
MA AG
Discovered
Apr 6, 2023MA AG + MT AG + NH AG +1Jun 8, 2023ME AGAug 16, 2023OR AG + ME AGAug 22, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + MT AG + NH AG +2
Attack vector
Unauthorized Access
MA 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)

8,973

Sum of filed state slices

266· 3.0% of stated

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

US8,973
MA181
MT54
ME20
NH11

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 filing13 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

106 days

Cadence

~1 / 8.8d

vs. multi-state median

13.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.