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

U.S. Waffle Inc — January 2023 breach

Clustered 3 filings across 3 jurisdictions · filed Sep 26, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

5,269

First → last filing

Sep 26, 2023

Merge confidence

100%

incident inc_1f8d603d37fc46d4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe a phishing attack. Intrusion Jan 18, 2023–Mar 3, 2023, discovered Jun 30, 2023 — the first regulatory filing landed 88 days later. 5,269 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
88days

Discovered → first regulatory filing

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine⏱ ME AG >30d · 88dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jan 18, 2023breach begins
Jun 30, 2023discovered
notification delay · 88 days
Sep 26, 2023first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. SEP 26MA AGMA AG noticefirst filing · 1 MA residentsday 0
  2. SEP 26SC AGSC AG notice2,558 SC residentsday 0
  3. SEP 26ME AGME AG noticemost recent · 2,710 affectedday 0
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 18, 2023 – Mar 3, 2023
SC AG
Discovered
Jun 30, 2023· 163d undetected
ME AG
Data types
Credentials · Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
MA AG + ME AG + SC AG
Attack vector
Phishing
SC AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

ME2,710
SC2,558
MA1

State AGs report only their own residents; teal bars show each state's reported slice.

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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