DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 5 filings

Glucobit — May 2026 breach

Clustered 5 filings across 5 jurisdictions · filing window Jun 1, 2026 → Jul 1, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

43,902

First → last filing

Jun 1, 2026 → Jul 1, 2026

Merge confidence

100%

incident inc_810af24b5417480f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filing describes hacking. Intrusion May 1, 2026, discovered May 1, 2026 — the first regulatory filing landed 31 days later (flagged late). 43,902 individuals reported across the linked filings. Data reported: Health (basic), PII, Identity (basic), and 1 more. Notifications rolled out on a 30-day schedule across 5 filings beginning Jun 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
31days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
30days

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 clocksOregon✗ OR AG >45dTexas✗ TX AG >30dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Incident timeline

May 1, 2026breach begins
May 1, 2026discovered
notification delay · 31 days
Jun 1, 2026first filing
Jul 1, 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 30OR AGOR AG noticestates nationwide total 43,902+29d
  3. JUN 30CA AGCA AG noticeno count stated+29d
  4. JUN 30WA AGWA AG notice3,181 WA residents+29d
  5. JUL 1TX AGTX AG noticemost recent · states nationwide total 43,902+30d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 1, 2026
OR AG
Discovered
May 1, 2026
IL AG + OR AG + WA AG +1
Data types
Health (basic) · Identity (basic) · PHI · PII
IL AG + TX AG + CA AG +1

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)

43,902

Sum of filed state slices

9,521· 21.7% of stated

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

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

30 days

Cadence

~1 / 7.5d

vs. multi-state median

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