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

PANDA RESTAURANT GROUP, INC. — March 2024 breach

Clustered 9 filings across 9 jurisdictions · filing window Apr 1, 2024 → May 1, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

239,815

First → last filing

Apr 1, 2024 → May 1, 2024

Merge confidence

100%

incident inc_bcbe2ddc59684fcd · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Mar 7, 2024–Mar 11, 2024, discovered Mar 7, 2024 — the first regulatory filing landed 25 days later (flagged late). 239,815 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 30-day schedule across 9 filings beginning Apr 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
25days

Discovered → first regulatory filing

Discovery variance
3days

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 >45dMaine⏱ ME AG >30d · 51dWashington⏱ WA AG >30dVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 7, 2024breach begins
Mar 7, 2024discovered · members disagree
notification delay · 25 days
Apr 1, 2024first filing
May 1, 2024most 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. APR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 29NH AGNH AG noticeno count stated+28d
  3. APR 30OR AGOR AG noticestates nationwide total 239,815+29d
  4. APR 30ME AGME AG notice64 affected+29d
  5. APR 30CA AGCA AG noticeno count stated+29d
  6. APR 30WA AGWA AG notice6,916 WA residents+29d
  7. APR 30VT AGVT AG noticeno count stated+29d
  8. APR 30MT AGMT AG notice959 MT residents+29d
  9. MAY 1MA AGMA AG noticemost recent · 444 MA residents+30d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 7, 2024 – Mar 11, 2024
NH AG
Discovered
Mar 7, 2024IL AGMar 10, 2024NH AG + OR AG + ME AG +4filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
NH AG + CA AG + WA AG +4
Attack vector
Unauthorized Access
NH 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)

239,815

Sum of filed state slices

8,383· 3.5% of stated

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

US239,815
WA6,916
MT959
MA444
ME64

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

30 days

Cadence

~1 / 3.8d

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.