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

Oregon Zoo — December 2023 breach

Clustered 9 filings across 9 jurisdictions · filing window Aug 15, 2024 → Aug 16, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

117,815

First → last filing

Aug 15, 2024 → Aug 16, 2024

Merge confidence

100%

incident inc_0dfe1f6d9d774244 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe hacking. Intrusion Dec 20, 2023–Jun 26, 2024, discovered Jun 26, 2024 — the first regulatory filing landed 50 days later. 117,815 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
50days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
1days

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 >14 bdayMaine⏱ ME AG >30d · 51dWashington⏱ WA AG >30dCalifornia✓ CA 60-day OK · 51dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 20, 2023breach begins
Jun 26, 2024discovered
notification delay · 50 days
Aug 15, 2024first filing
Aug 16, 2024most 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 15VT AGVT AG noticefirst filing · no count statedday 0
  2. AUG 16NH AGNH AG noticeno count stated+1d
  3. AUG 16MA AGMA AG notice309 MA residents+1d
  4. AUG 16IN AGIN AG noticestates nationwide total 117,815+1d
  5. AUG 16CA AGCA AG noticeno count stated+1d
  6. AUG 16ME AGME AG noticestates nationwide total 117,815+1d
  7. AUG 16OR AGOR AG noticestates nationwide total 117,815+1d
  8. AUG 16MT AGMT AG notice474 MT residents+1d
  9. AUG 16WA AGWA AG noticemost recent · 22,901 WA residents+1d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 20, 2023 – Jun 26, 2024
VT AG
Discovered
Jun 26, 2024· 189d undetected
VT AG + CA AG + ME AG +2
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
VT AG + NH AG + CA AG +4
Attack vector
Third-Party / Supply Chain
VT 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)

117,815

Sum of filed state slices

24,041· 20.4% of stated

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

US117,815
WA22,901
MT474
MA309
IN200
ME157

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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