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

Tulane University — August 2025 breach

Clustered 12 filings across 12 jurisdictions · filing window Aug 10, 2025 → May 14, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

11

Affected · reported

80,867

First → last filing

Aug 10, 2025 → May 14, 2026

Merge confidence

100%

incident inc_4017b3cc085d458f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 10, 2025, discovered Aug 10, 2025. 80,867 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 277-day schedule across 11 filings beginning Aug 10, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
0days

Discovered → first regulatory filing

Discovery variance
214days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 104d

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
277days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dTexas✗ TX AG >30dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 61dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 10, 2025breach begins
Aug 10, 2025discovered · members disagree
notification delay · 0 days
Aug 10, 2025first filing
May 14, 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. AUG 10MT AGMT AG noticefirst filing · 50 MT residentsday 0
  2. NOV 21Leak sitecl0p postattacker claim · unverified+104d
  3. APR 2IN AGIN AG noticestates nationwide total 80,867+235d
  4. APR 2NE AGNE AG notice74 NE residents+235d
  5. MAY 1IL AGIL AG noticeno count stated+264d
  6. MAY 12NH AGNH AG notice170 NH residents+275d
  7. MAY 12OR AGOR AG noticestates nationwide total 80,867+275d
  8. MAY 12VT AGVT AG notice69 VT residents+275d
  9. MAY 12MA AGMA AG notice1,294 MA residents+275d
  10. MAY 12CA AGCA AG noticeno count stated+275d
  11. MAY 12ME AGME AG notice127 ME residents+275d
  12. MAY 14TX AGTX AG noticemost recent · states nationwide total 80,867+277d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 10, 2025
MT AG
Discovered
Aug 10, 2025MT AG + NE AGOct 2, 2025OR AGMar 12, 2026IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Employment · Financial account · Identity (basic) · Government ID · PCI · PII
MT AG + NE AG + NH AG +6
Attack vector
Unauthorized Access
MT 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)

80,867

Sum of filed state slices

5,049· 6.2% of stated

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

US80,867
TX2,992
MA1,294
IN273
NH170
ME127
NE74
VT69
MT50

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

277 days

Cadence

~1 / 25.2d

vs. multi-state median

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