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

O’Connor — November 2024 breach

Clustered 10 filings across 9 jurisdictions · filing window Jan 31, 2025 → Sep 25, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

11,644

First → last filing

Jan 31, 2025 → Sep 25, 2025

Merge confidence

100%

incident inc_60031453e8054b5d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Nov 23, 2024–Dec 1, 2024, discovered Dec 2, 2024 — the first regulatory filing landed 60 days later. 11,644 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 237-day schedule across 8 filings beginning Jan 31, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
53days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 218d

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 7dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 23, 2024breach begins
Dec 2, 2024discovered · members disagree
notification delay · 60 days
Jan 31, 2025first filing
Feb 10, 2025most 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. JAN 31MA AGMA AG noticefirst filing · 4,519 MA residentsday 0
  2. JAN 31ME AGME AG notice1,088 ME residentsday 0
  3. JAN 31NE AGNE AG notice2 NE residentsday 0
  4. JAN 31IN AGIN AG noticestates nationwide total 11,644day 0
  5. JAN 31NH AGNH AG notice1,314 NH residentsday 0
  6. JAN 31VT AGVT AG noticeno count statedday 0
  7. JAN 31MT AGMT AG notice12 MT residentsday 0
  8. FEB 10RI AGRI AG notice678 RI residents+10d
  9. SEP 6Leak siteqilin postattacker claim · unverified+218d
  10. SEP 25Leak siteqilin postmost recent · attacker claim · unverified+237d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 23, 2024 – Dec 1, 2024
ME AG
Discovered
Dec 2, 2024NE AG + NH AG + VT AG +2Jan 24, 2025ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + NE AG +4
Attack vector
Unauthorized Access
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)

11,644

Sum of filed state slices

7,639· 65.6% of stated

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

US11,644
MA4,519
NH1,314
ME1,088
RI678
IN26
MT12
NE2

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

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

237 days

Cadence

~1 / 26.3d

vs. multi-state median

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