DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblackbytehigh sensitivity
Merged incident · 7 filings

Napa Valley College — June 2022 breach

Clustered 7 filings across 7 jurisdictions · filing window Jun 26, 2022 → Sep 12, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

9,341

First → last filing

Jun 26, 2022 → Sep 12, 2022

Merge confidence

100%

incident inc_150499493d474117 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. Intrusion Jun 10, 2022, discovered Jun 10, 2022 — the first regulatory filing landed 76 days later. 9,341 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 78-day schedule across 6 filings beginning Jun 26, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
76days

Discovered → first regulatory filing

Discovery variance
69days

Range of discovered_at dates across filings

Leak precedence
60days 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
78days

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 >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 10, 2022breach begins
Jun 10, 2022discovered · members disagree
notification delay · 76 days
Aug 25, 2022first filing
Sep 12, 2022most 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. JUN 26Leak siteblackbyte postfirst filing · attacker claim · unverifiedday 0
  2. AUG 25ME AGME AG noticestates nationwide total 9,341+60d
  3. SEP 6IN AGIN AG noticestates nationwide total 9,341+72d
  4. SEP 6CA AGCA AG noticeno count stated+72d
  5. SEP 6MT AGMT AG notice15 MT residents+72d
  6. SEP 6MA AGMA AG notice12 MA residents+72d
  7. SEP 12NH AGNH AG noticemost recent · 5 NH residents+78d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 10, 2022
ME AG
Discovered
Jun 10, 2022CA AG + MT AG + NH AGAug 18, 2022ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
ME AG + CA AG + MT AG +2
Attack vector
Ransomware
ME 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)

9,341

Sum of filed state slices

48· 0.5% of stated

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

US9,341
MT15
IN12
MA12
NH5
ME4

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

78 days

Cadence

~1 / 13d

vs. multi-state median

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