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

American Association of Colleges of Osteopathic Medicine — September 2024 breach

Clustered 11 filings across 11 jurisdictions · filed Apr 8, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

67,804

First → last dated filing

Apr 8, 2025

Merge confidence

100%

incident inc_d3cfd18a0c1243e7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Sep 26, 2024, discovered Sep 26, 2024. 67,804 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
186days

Range of discovered_at dates across filings

Filing span
0days

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 bdayCalifornia✗ CA 60-day late · 194dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 194dIowa✓ IA AG ≤5 bdayDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 26, 2024breach begins
Sep 26, 2024discovered · members disagree
Apr 8, 2025first dated filing
—watching for filings

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

  1. APR 1IL AGIL AG noticefiling day not on record · no count stated—
  2. APR 8IA AGIA AG noticefirst filing · 631 IA residentsday 0
  3. APR 8VT AGVT AG noticeno count statedday 0
  4. APR 8NE AGNE AG noticefiling day not on record · 288 NE residents—
  5. APR 8NH AGNH AG notice259 NH residentsday 0
  6. APR 8OR AGOR AG noticestates nationwide total 67,804day 0
  7. APR 8CA AGCA AG noticeno count statedday 0
  8. APR 8ME AGME AG noticestates nationwide total 67,804day 0
  9. APR 8MT AGMT AG notice274 MT residentsday 0
  10. APR 8IN AGIN AG noticestates nationwide total 67,804day 0
  11. APR 8WA AGWA AG noticemost recent · 1,740 WA residentsday 0
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 26, 2024
OR AG
Discovered
Sep 26, 2024IL AG + IA AG + VT AG +6Mar 31, 2025OR AGfilings disagree on discovery
Data types
Credentials · Education · Financial account · Health (basic) · Identity (basic) · Government ID · PII
IL AG + IA AG + NE AG +6
Attack vector
Phishing
IA 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)

67,804

Sum of filed state slices

4,766· 7.0% of stated

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

US67,804
WA1,740
IN1,146
IA631
ME428
NE288
MT274
NH259

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 filing11 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 12, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

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