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

The Burton Corporation — February 2023 breach

Clustered 9 filings across 6 jurisdictions · filing window Mar 27, 2023 → May 31, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

5,282

First → last filing

Mar 27, 2023 → May 31, 2023

Merge confidence

100%

incident inc_55b211bd16ad4359 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Feb 11, 2023, discovered Feb 11, 2023 — the first regulatory filing landed 44 days later. 5,282 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 65-day schedule across 9 filings beginning Mar 27, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
44days

Discovered → first regulatory filing

Discovery variance
55days

Range of discovered_at dates across filings

Filing span
65days

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 clocksMaine⏱ ME AG >30d · 49dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 11, 2023breach begins
Feb 11, 2023discovered · members disagree
notification delay · 44 days
Mar 27, 2023first filing
May 31, 2023most 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. MAR 27MT AGMT AG noticefirst filing · 1 MT residentsday 0
  2. MAR 28MA AGMA AG notice359 MA residents+1d
  3. MAR 28ME AGME AG noticestates nationwide total 737+1d
  4. APR 3NH AGNH AG notice5 NH residents+7d
  5. MAY 26ME AGME AG noticestates nationwide total 5,282+60d
  6. MAY 26CA AGCA AG noticeno count stated+60d
  7. MAY 26IN AGIN AG noticestates nationwide total 5,282+60d
  8. MAY 26MT AGMT AG notice1 MT residents+60d
  9. MAY 31NH AGNH AG noticemost recent · 54 NH residents+65d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 11, 2023
ME AG
Discovered
Feb 11, 2023MT AG + NH AG + CA AGMar 9, 2023ME AGApr 7, 2023ME AGfilings disagree on discovery
Data types
Credentials · Employment · Financial account · Identity (basic) · Government ID · PII
MT AG + ME AG + NH AG +2
Attack vector
Unauthorized Access
MT 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)

5,282

Sum of filed state slices

477· 9.0% of stated

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

US5,282
MA359
NH54
ME52
IN11
MT1

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
Reviewed
operator-reviewed Jun 12, 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

65 days

Cadence

~1 / 8.1d

vs. multi-state median

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