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

Five Guys Holdings, Inc. — May 2018 breach

Clustered 5 filings across 3 jurisdictions · filing window Nov 2, 2018 → Dec 3, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

not comparable

First → last filing

Nov 2, 2018 → Dec 3, 2018

Merge confidence

100%

incident inc_564acce157dc4eed · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a phishing attack. Intrusion May 23, 2018–Aug 6, 2018, discovered Aug 6, 2018 — the first regulatory filing landed 88 days later (flagged late). Data reported: Government ID, Identity (basic), Employment, and 4 more. Notifications rolled out on a 31-day schedule across 5 filings beginning Nov 2, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
88days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
31days

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 clocksCalifornia✗ CA 60-day late · 115dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 23, 2018breach begins
Aug 6, 2018discovered
notification delay · 88 days
Nov 2, 2018first filing
Dec 3, 2018most 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. NOV 2CA AGCA AG noticefirst filing · no count statedday 0
  2. NOV 2MT AGMT AG notice1 MT residentsday 0
  3. NOV 6NH AGNH AG notice5 NH residents+4d
  4. NOV 30CA AGCA AG noticeno count stated+28d
  5. DEC 3NH AGNH AG noticemost recent · 3 NH residents+31d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 23, 2018 – Aug 6, 2018
CA AG
Discovered
Aug 6, 2018· 75d undetected
CA AG + MT AG + NH AG
Data types
Credentials · Employment · Financial · Financial account · Identity (basic) · Government ID · PII
CA AG + MT AG + NH AG
Attack vector
Phishing
CA AG

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

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

31 days

Cadence

~1 / 7.8d

vs. multi-state median

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