DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 5 filings

Murray's Cheese — February 2026 breach

Clustered 5 filings across 5 jurisdictions · filing window Feb 21, 2026 → May 27, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

192

First → last filing

Feb 21, 2026 → May 27, 2026

Merge confidence

100%

incident inc_134ee69bff8d477d · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 15, 2026–Feb 21, 2026, discovered Feb 21, 2026 — the first regulatory filing landed 59 days later. 192 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 95-day schedule across 4 filings beginning Feb 21, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
59days 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
95days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts⏱ MA AG >30dMaine⏱ ME AG >30d · 59dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 15, 2026breach begins
Feb 21, 2026discovered
notification delay · 59 days
Apr 21, 2026first filing
May 27, 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. FEB 21Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. APR 21MA AGMA AG notice1 MA residents+59d
  3. APR 21ME AGME AG notice5 ME residents+59d
  4. APR 21IN AGIN AG noticestates nationwide total 192+59d
  5. MAY 27NH AGNH AG noticemost recent · 1 NH residents+95d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 15, 2026 – Feb 21, 2026
MA AG
Discovered
Feb 21, 2026· 6d undetected
MA AG + ME AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + ME AG + NH AG
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)

192

Sum of filed state slices

9· 4.7% of stated

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

US192
ME5
IN2
MA1
NH1

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 filing4 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 16, 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

95 days

Cadence

~1 / 23.8d

vs. multi-state median

11.9× 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.