DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed17 filings · 15 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhuntershigh sensitivity
Merged incident · 17 filings

The Trustees of the University of Pennsylvania — August 2025 breach

Clustered 17 filings across 16 jurisdictions · filing window Dec 1, 2025 → Apr 15, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

15

Affected · reported

442,500

First → last filing

Dec 1, 2025 → Apr 15, 2026

Merge confidence

100%

incident inc_9f1e9cbf120c4ee7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Aug 9, 2025–Oct 31, 2025, discovered Sep 29, 2025 — the first regulatory filing landed 63 days later (flagged late). 442,500 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 135-day schedule across 16 filings beginning Dec 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
63days

Discovered → first regulatory filing

Discovery variance
43days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 65d

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dVermont✓ VT AG ≤14 bdayIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueMaine✓ ME AG ≤30d · 20dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 9, 2025breach begins
Sep 29, 2025discovered · members disagree
notification delay · 63 days
Dec 1, 2025first filing
Apr 15, 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. DEC 1IN AGIN AG noticefirst filing · 2,067 IN residentsday 0
  2. DEC 1CA AGCA AG noticeno count statedday 0
  3. DEC 1MT AGMT AG notice465 MT residentsday 0
  4. DEC 1VT AGVT AG noticeno count statedday 0
  5. DEC 1IA AGIA AG notice752 IA residentsday 0
  6. DEC 1SC AGSC AG notice2,578 SC residentsday 0
  7. DEC 1IL AGIL AG noticeno count statedday 0
  8. DEC 1ME AGME AG notice1,488 ME residentsday 0
  9. DEC 1DE AGDE AG noticeno count statedday 0
  10. DEC 1WA AGWA AG notice6,413 WA residentsday 0
  11. DEC 1NE AGNE AG noticeno count statedday 0
  12. DEC 2MA AGMA AG notice16,963 MA residents+1d
  13. DEC 3TX AGTX AG noticestates nationwide total 442,500+2d
  14. DEC 4NH AGNH AG notice1,588 NH residents+3d
  15. DEC 22OR AGOR AG noticestates nationwide total 2,722+21d
  16. FEB 4Leak siteshinyhunters postattacker claim · unverified+65d
  17. APR 15WA AGWA AG noticemost recent · 5,878 WA residents+135d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 9, 2025
IN AG
Discovered
Sep 29, 2025WA AGOct 31, 2025WA AGNov 11, 2025MT AG + VT AG + IA AG +8filings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
CA AG + VT AG + IA AG +10
Attack vector
Third-Party / Supply Chain
CA 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)

442,500

Sum of filed state slices

43,769· 9.9% of stated

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

US442,500
MA16,963
TX11,455
WA6,413
SC2,578
IN2,067
NH1,588
ME1,488
IA752
MT465

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 filing16 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 25, 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

135 days

Cadence

~1 / 8.4d

vs. multi-state median

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