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

Pacific Union College — March 2023 breach

Clustered 9 filings across 9 jurisdictions · filing window May 30, 2023 → Nov 16, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

56,041

First → last filing

May 30, 2023 → Nov 16, 2023

Merge confidence

100%

incident inc_350752523be2412c · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 5, 2023–Mar 19, 2023, discovered Mar 19, 2023 — the first regulatory filing landed 233 days later (flagged late). 56,041 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 4 more. Notifications rolled out on a 170-day schedule across 8 filings beginning May 30, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
233days

Discovered → first regulatory filing

Discovery variance
233days

Range of discovered_at dates across filings

Leak precedence
161days 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
170days

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 >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 5, 2023breach begins
Mar 19, 2023discovered · members disagree
notification delay · 233 days
Nov 7, 2023first filing
Nov 16, 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 30Leak sitetrigona postfirst filing · attacker claim · unverifiedday 0
  2. NOV 7OR AGOR AG noticestates nationwide total 56,041+161d
  3. NOV 7MA AGMA AG notice59 MA residents+161d
  4. NOV 7CA AGCA AG noticeno count stated+161d
  5. NOV 7MT AGMT AG notice35 MT residents+161d
  6. NOV 8ME AGME AG noticestates nationwide total 56,041+162d
  7. NOV 9VT AGVT AG noticeno count stated+163d
  8. NOV 13NH AGNH AG notice5 NH residents+167d
  9. NOV 16WA AGWA AG noticemost recent · 1,921 WA residents+170d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 5, 2023 – Mar 19, 2023
OR AG
Discovered
Mar 19, 2023MT AG + WA AGOct 9, 2023OR AG + ME AGNov 7, 2023NH AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + CA AG + NH AG +4
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)

56,041

Sum of filed state slices

2,042· 3.6% of stated

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

US56,041
WA1,921
MA59
MT35
ME22
NH5

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 filing8 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 22, 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

170 days

Cadence

~1 / 21.3d

vs. multi-state median

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