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

ACADEMY MORTGAGE CORPORATION — March 2023 breach

Clustered 11 filings across 10 jurisdictions · filing window May 14, 2023 → Jan 15, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

284,443

First → last filing

May 14, 2023 → Jan 15, 2024

Merge confidence

100%

incident inc_c7cbd33c612a4979 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 21, 2023, discovered Mar 21, 2023 — the first regulatory filing landed 273 days later (flagged late). 284,443 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Employment. Notifications rolled out on a 246-day schedule across 10 filings beginning May 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
273days

Discovered → first regulatory filing

Discovery variance
252days

Range of discovered_at dates across filings

Leak precedence
219days 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
246days

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 · 274dMaine✗ ME AG >90d · 300dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 21, 2023breach begins
Mar 21, 2023discovered · members disagree
notification delay · 273 days
Dec 19, 2023first filing
Jan 15, 2024most 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 14Leak sitealphv postfirst filing · attacker claim · unverifiedday 0
  2. DEC 19NH AGNH AG notice214 NH residents+219d
  3. DEC 20IN AGIN AG noticestates nationwide total 284,443+220d
  4. DEC 27WA AGWA AG notice17,083 WA residents+227d
  5. DEC 27MT AGMT AG notice262 MT residents+227d
  6. JAN 5CA AGCA AG noticeno count stated+236d
  7. JAN 5OR AGOR AG noticestates nationwide total 284,443+236d
  8. JAN 8SC AGSC AG notice3,594 SC residents+239d
  9. JAN 15ME AGME AG noticestates nationwide total 284,443+246d
  10. JAN 15MA AGMA AG notice5,354 MA residents+246d
  11. JAN 15CA AGCA AG noticemost recent · no count stated+246d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 21, 2023
NH AG
Discovered
Mar 21, 2023NH AG + WA AG + MT AG +3Nov 28, 2023OR AGfilings disagree on discovery
Data types
Employment · Identity (basic) · Government ID
NH AG + WA AG + MT AG +4
Attack vector
Unauthorized Access
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)

284,443

Sum of filed state slices

32,109· 11.3% of stated

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

US284,443
WA17,083
MA5,354
IN4,984
SC3,594
ME618
MT262
NH214

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
Reviewed
operator-reviewed Jun 24, 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

246 days

Cadence

~1 / 24.6d

vs. multi-state median

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